Using Derby "Edge"

Derby has a fairly spaced-out release cycle, and in order to keep up with the latest improvements, bug-fixes, and other-module compatibilities, some find it useful to depend on Derby "edge" in their app's package.json. This is poor practice in production deployments - instead your package.json dependencies should be version-specific to avoid compatibility issues; but if you're willing to live on the bleeding edge, follow this guide.

To use Derby edge, you specify the Github URL in package.json (see Git URLs as Dependencies). Unfortunately for our case, Derby itself depends on a frozen Racer version (currently 0.3.13), so don't use git://github.com/codeparty/derby; instead, you need to fork Derby, edit it's package.json to point to "racer": "git://github.com/codeparty/racer#master", and use your own Github fork in your application's package.json. You can use mine if you prefer: "derby":"git://github.com/lefnire/derby#master", which I'll try to keep up with HEAD. See this example package.json. Ideally codeparty/derby#master would use codeparty/racer#master between all tagged releases.

(note, this may be unnecessary - see this comment)