Question: where does todo-mvc/static/deps.js come from?

[k0001]

Hey @Boothead, I wonder where does todo-mvc/static/deps.js come from. How do you generate that file?

[commandodev]

@krisajenkins wrote that to pull in the dependencies, we then used browserify to build vendor.js. I'm sure there's an equivalent ghcjs way to do but I haven't tried too hard. I've very open to improvement suggestions :-)

[krisajenkins]

For what it's worth I wrote:

global.Delegator = require('dom-delegator');
global.Delegator();
global.h = require('virtual-hyperscript');
global.svg = require('virtual-hyperscript/svg');
global.hook = require('virtual-hyperscript/hooks/ev-hook');
global.diff = require('virtual-dom/diff');
global.patch = require('virtual-dom/patch');
global.createElement = require('virtual-dom/create-element');

Browserify turns that code into that larger script that's in the repo. :-}

[k0001]

Thanks for the explanation!
Le 27 janv. 2015 19:01, "Kris Jenkins" notifications@github.com a écrit :

For what it's worth I wrote:

global.Delegator = require('dom-delegator');global.Delegator();global.h = require('virtual-hyperscript');global.svg = require('virtual-hyperscript/svg');global.hook = require('virtual-hyperscript/hooks/ev-hook');global.diff = require('virtual-dom/diff');global.patch = require('virtual-dom/patch');global.createElement = require('virtual-dom/create-element');

Browserify turns that code into that larger script that's in the repo. :-}

—
Reply to this email directly or view it on GitHub
#2 (comment).