Setting Up a Client Side JS Dev Environment With node.js - Part 2
Edit 2015/03/14: This post was written a couple of years ago so is a bit outdated now. Express in particular has changed quite a bit since this was written
This is another post in my puzzli series.
I’ve already set up node in part 1, to serve up a simple page to use as a JS development environment. Next I’ll be setting up jasmine so I can do TDD on the client side code for puzz.li. This commits for this post are from where we left off on the previous post, up to this commit.
First a quick diversion about dependency management. Up until now I’d just been doing:
npm install <modulename>
However unless I check all the node_modules I’ve added into git, as more and more dependencies are added deploying the app elsewhere will become a bit tricky. The solution to this problem is to create a package.json file, where you can define dependencies. This is what mine looks like so far:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
As you can see it gives a bit of info about the package itself, as well as defining the dependencies to get it up and running. Now when checking the app out from the github repo, it just requires a single command:
and all the dependencies of the right version will be grabbed automatically as you’d expect.
Back to setting up jasmine now. We kick off by install jasmine-node, a module that sets up jasmine nicely in a node environment, and supports specs written in coffeescript as well. As we (hopefully) won’t need jasmine-node to actually deploy the app to production, we can add it into package.json as a devDependency like so:
1 2 3 4 5 6 7
Finally, we just need to set up a simple link to jasmine’s script runner so it’s nice and accessible:
$ ln -s node_modules/jasmine-node/bin/jasmine-node run_specs $ chmod u+x run_specs
Let’s see if everything’s working by trying to get a simple always-true spec running.
1 2 3 4 5
and now we run it with our new command:
$ ./run_specs --coffee spec . Finished in 0.008 seconds 1 test, 1 assertion, 0 failures
We’re finally in a position to get underway with actually building something, and that will be the subject of the next post.