So yes I’d argue that the package.json was a big improvement, but you’re right that it could be further improved. Embedding shell scripts in JSON isn’t exactly pretty.
]]>b) I don’t notice my live builds being slow. One second from changing a file to seeing the changes reflect in the browser.
c) Yup, glorious, simple shell scripts. Love ’em.
]]>I still use gulp, but I don’t want to force others to install gulp globally, so I do this:
“dependencies”: {
“gulp”: “latest”
},
“scripts”: {
“start”: “gulp build”
}
This will also let me switch to the next shinier gulp replacement without changing my build instructions at all. npm scripts are great, but it doesn’t have to be all or nothing.
]]>Still, in a post-ES6 we’ll still need build systems. Your JS in a complex app will still need to be minified and concatenated, and the build handles other tasks like compiling LESS to CSS and generating regular versions of retina images.
Cheers,
Bernie :o)
]]>