Closed user471 closed 8 years ago
It gets built on prepublish to npm, so we don't need to keep the built files in the repo. Is there some reason you needed it?
Maybe I did something wrong.
npm build
browserify lib/index.js -o out.js
But the out.js doesn't have global deku object.
try npm install
.
@user471 is right, it won't give you the global, standalone version that way. We might need to make a standalone
task that runs browserify src/index.js -s deku -t babelify -o dist/deku.js
.
browserify src/index.js -s deku -t babelify -o dist/deku.js
It works. I think separate task would be useful
Added it as npm run standalone
Thought about rollup? It is better suited for publishing libraries than webpack or browserify (which themselves are better for building applications).
I'd be ok with that, the tree shaking alone makes it awesome. If someone wants to just swap that out, go for it, I haven't actually used Rollup yet.
Bundling to an IIFE is very good too instead of webpack or browserify exporting a variable but still having internal implementation of require. I'll make a pull request.
Why there isn't dist folder in latest releases?