Marcello Bastéa-Forte

@Rich-Harris the weird part is that he's not getting this error: `throw new Error( 'Could not find Ractive! It must be loaded before the Ractive-transitions-slide plugin' );` Clearly a Ractive...

@doctyper could you gist the browserify output of that code you just pasted? Maybe something will reveal there...

You're right, ractify is requiring the runtime-only build, so that will cause a problem (from the gist, it also looks like there's a problem due to OS X case-sensitivity). I...

I wouldn't worry about the ractify api too much, I can change it. The way it works today: `require('ractify')` is a shorthand for, and will return the same js object...

As an aside, npm wasn't always case sensitive: https://github.com/npm/npm/issues/3914#issuecomment-24878907

Because ractify works in browserify, the script code is wrapped in a module wrapper function which exposes `require` (and `exports` and `module`). Ractify just generates the javascript that goes in...

The latest version of ractify does not require any version of ractive for you, that means you can use the non-runtime version of Ractive (`require('ractive')`), which in theory should match...

The intention is so you can upgrade ractive without my having to release an update to ractify each time.

I've gone back and forth on this. The issue I ran into when I did it that way is that your project also needs to depend on ractive in order...