When the directory structure of your Node.js application (not library!) has some depth, you end up with a lot of annoying relative paths in your require calls like:
const Article = require('../../../../app/models/article');Those suck for maintenance and they're ugly.
| #!/usr/bin/bash | |
| ############################################## | |
| #from http://zeromq.org/intro:get-the-software | |
| ############################################## | |
| #get zeromq | |
| wget http://download.zeromq.org/zeromq-4.0.5.tar.gz | |
| #unpack tarball package |
Do you need Promises and other ES6 goodness. This will give you polyfills for your tests, and a working Karma, Browserify & Babelify setup.
This example has been drawn up for this StackOverflow question. You probably want to polyfill Promises, etc. unless all your supported browsers already contain it. You probably also want to keep your compilation/babelification/browserification process the same between build and test. Fortunately you can (hint: common config can live in package.json), but that's outside of the scope of this Gist.
