Using Derby "Edge"

Derby releases are far-between, and in order to keep up with the latest improvements, bug-fixes, and other-module compatibilities you'll want to depend on Derby "edge" in your app's package.json. Once Derby stabilizes you should use pinned versions to avoid compatibility issues; but while it's still in development, use 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)

Edit your package.json to look like this (see this working example):

{
  ...
  "dependencies": {
    "derby": "git://github.com/Unroll-Me/derby#master",
    "racer": "git://github.com/SLaks/racer#master",
  }
  ...
}

Then run rm -rf node_modules && npm install. Note: presently recommending SLaks' fork of Racer & Derby (Unroll-Me/Derby is SLaks), which provide huge bug fixes, optimizations, and new features. Once they're merged into upstream, we'll edit this page back to codeparty/racer#master & codeparty/derby#master

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

##Creating New Projects In order to use Edge for new projects with derby new first-project, you'll need to install Derby Edge globally npm install -g git://github.com/codeparty/derby#master, then edit your package.json as above. You may also hit some view binding syntax incompatibilities with new versions. Fogetaboutit - start with Derby Boilerplate instead, which will get you further faster.

##New Dom Bindings Syntax When using Edge, the Dom syntax as outlined in Derby's documentation won't work. Derby made a recent change in dom syntax, see this file for the details.