3 ms·
vim readme.md "To run, use 'npm run'. To develop, use 'npm run dev'. To test, use 'npm test'." Or, open up package.json and see what scripts are there... I do
by komali2 10y ago
vim readme.md
"To run, use 'npm run'. To develop, use 'npm run dev'. To test, use 'npm test'."
Or, open up package.json and see what scripts are there... I don't get how that's any different? Why wouldn't you have scripted all that?
- hoorayimhelping 10y agoI script it that way and then add a makefile on top of it so that it's conventional and handles things like envvar setting. build: NODE_ENV=production yarn build:server NODE_ENV=production yarn build:client test: NODE_ENV=test yarn test
- Klathmon 10y agowe do the same, but the npm scripts are just the "entry point". one of them was this: "build:dist": "NODE_ENV=production babel ./src --out-dir ./dist"
- ktRolster 10y agoMaybe you missed this paragraph, it talks about your point: Makefiles are more versatile