| To me the big difference is really to do with where the code operates. With Require.js you make changes to your code to be able to drive it, to avoid having a build step. Browserify you had to have a build step, but it operates on your code 'from the outside', to avoid having to modify it. Webpack does both of those. it has a build step, but it works by extending the require() format to be able to specify the transforms inside the code itself. The webpack configuration format is mostly just a way to replace require calls at runtime with a regular expression. I find that this is a lot more straight forward, powerful and explicit than the [1] filename extension checks that happen in most browserify transforms.
https://github.com/jnordberg/coffeeify/blob/master/index.js#... I made a presentation about webpack, if you want to see : http://adrianrossouw.github.io/webpack-mostly-just-works/ |