search

michaelficarra / commonjs-everywhere

:rainbow: minimal CommonJS browser bundler with aliasing, extensibility, and source maps
BSD 3-Clause "New" or "Revised" License
158 stars 21 forks source link

Explain how it differs from browserify #103

Open rauschma opened 10 years ago

rauschma commented 10 years ago

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).
briandipalma commented 10 years ago

And WebPack, I guess the difference is that it doesn't bundle files like html templates?

vendethiel commented 10 years ago

I bundle my jade/stylus file in.

briandipalma commented 10 years ago

Hey @Nami-Doc

I bundle my jade/stylus file in.

So there's a plugin for file (CSS/JSON/HTML) bundling that commonjs-everywhere can use? From my quick read of the front page README I didn't see one so I guessed that it didn't support such functionality.

vendethiel commented 10 years ago

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) ... The code for nephrite (my jade preprocessor)/stylus can be, for example, found here.

briandipalma commented 10 years ago

Right so it's done via handlers then. OK I see now, thank you.