Modern JavaScript for Ancient Web Developers

Re:Modern JavaScript for Ancient Web Developers by komali2 on Thursday March 23, 2017 @02:40PM (#13942753)

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?

[ Parent | on HN ]

Re:Modern JavaScript for Ancient Web Developers by hoorayimhelping on Thursday March 23, 2017 @03:40PM (#13943424)

I 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

[ Parent | on HN ]

Re:Modern JavaScript for Ancient Web Developers by Klathmon on Thursday March 23, 2017 @03:53PM (#13943578)

we 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"

[ Parent | on HN ]

Re:Modern JavaScript for Ancient Web Developers by ktRolster on Thursday March 23, 2017 @04:39PM (#13944031)

Maybe you missed this paragraph, it talks about your point:

Makefiles are more versatile

[ Parent | on HN ]