Nodejs browserify is terrific when building modular js apps. If gulp is part of the setup as well, the workflow is further enhanced to manage and resolve dependencies, properly bundle, uglify with sourcemaps, auto-polyfill, jshint, test... This is pretty handy for css as well with pre-processing, auto-prefixing, linting, embedding resources and generating documentation.
TL;DR: with npm/bower you get access to an extensive ecosystem of front-end libraries, making nodejs perfect for building (not necessarily serving!) client-side code. In fact, using it for client-side code is so awesome that npm, bower and grunt/gulp will be supported out of the box in VS 2015. In the meantime, we have set up a gulp task that runs pre-build and writes dist js/css (bundling output).
What's a good way to reference external static content with fingerprinted urls? In the long run we would ideally be able to separate client-side content icompletely so it could be independently built and deployed to CDN without having to build the rest of the application as well.
Aucun commentaire:
Enregistrer un commentaire