6 Matching Annotations
  1. Nov 2018
  2. Oct 2018
  3. Feb 2016
    1. but also it is extremely easy to transition from browserify to webpack when needed.
    2. If however, you’re predominantly dependent on the NPM ecosystem and you want a tool with a small and very well designed API and takes minimal configuration, you should go for Browserify

      We don't particularly need Node compatibility at the moment, but "small and well designed API" is appealing.

      On the other hand, not having to hunt around and collect all the tools together for packaging code for the browser is also appealing.

    1. This is probably the best high level comparison of the approach of Webpack and Browserify that I've seen.

  4. Sep 2015
    1. Talk from ng-conf 2014 with advice on how to integrate Browserify and Angular, dealing with the fact that both have their own module systems.