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). You'll also want to use Racer's Github repo to keep Derby & Racer in sync. (If Racer is specified in your own package.json, Derby will bypass it's own frozen 0.3.13 Racer install in favor or your top-level Racer install, see this discussion)

Your package.json file will look like this (also see this working example):

{
  ...
  "dependencies": {
    "derby": "git://github.com/codeparty/derby#master",
    "racer": "git://github.com/codeparty/racer#master",
  }
  ...
}

Windows users, if you're having trouble see this comment.