New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Explain how it differs from browserify #103
Comments
And WebPack, I guess the difference is that it doesn't bundle files like html templates? |
I bundle my jade/stylus file in. |
Hey @Nami-Doc
So there's a plugin for file (CSS/JSON/HTML) bundling that commonjs-everywhere can use? |
Not using any "plugins". It's pretty dumb to republish a whole set of plugins for every bundler that comes around (definitely one of the failures of the node community) ... |
Right so it's done via handlers then. OK I see now, thank you. |
Given browserify’s popularity, it probably makes sense to describe in the readme how CommonJS Everywhere is different from it.
--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/2268391-explain-how-it-differs-from-browserify?utm_campaign=plugin&utm_content=tracker%2F297897&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F297897&utm_medium=issues&utm_source=github).The text was updated successfully, but these errors were encountered: