Need advice about which tool to choose?Ask the StackShare community!

Browserify

586
389
+ 1
262
Webpack

26.3K
18.1K
+ 1
751
Add tool

Browserify vs Webpack: What are the differences?

Browserify: Browser-side require() the node.js way. Browserify lets you require('modules') in the browser by bundling up all of your dependencies; Webpack: A bundler for javascript and friends. A bundler for javascript and friends. Packs many modules into a few bundled assets. Code Splitting allows to load parts for the application on demand. Through "loaders" modules can be CommonJs, AMD, ES6 modules, CSS, Images, JSON, Coffeescript, LESS, ... and your custom stuff.

Browserify and Webpack are primarily classified as "Front End Package Manager" and "JS Build Tools / JS Task Runners" tools respectively.

"Node style browser code" is the primary reason why developers consider Browserify over the competitors, whereas "Most powerful bundler" was stated as the key factor in picking Webpack.

Browserify and Webpack are both open source tools. It seems that Webpack with 49.5K GitHub stars and 6.22K forks on GitHub has more adoption than Browserify with 12.7K GitHub stars and 1.12K GitHub forks.

Instagram, Pinterest, and 9GAG are some of the popular companies that use Webpack, whereas Browserify is used by Cloudflare, Inc., UNION, and Chooos. Webpack has a broader approval, being mentioned in 2181 company stacks & 1298 developers stacks; compared to Browserify, which is listed in 111 company stacks and 42 developer stacks.

Decisions about Browserify and Webpack
Aleksandr Filatov
Contract Software Engineer - Microsoft · | 0 upvote · 78.8K views
Why migrated?

I could define the next points why we have to migrate:

  • Decrease build time of our application. (It was the main cause).
  • Also jspm install takes much more time than npm install.
  • Many config files for SystemJS and JSPM. For Webpack you can use just one main config file, and you can use some separate config files for specific builds using inheritance and merge them.
See more

We mostly use rollup to publish package onto NPM. For most all other use cases, we use the Meteor build tool (probably 99% of the time) for publishing packages. If you're using Node on FHIR you probably won't need to know rollup, unless you are somehow working on helping us publish front end user interface components using FHIR. That being said, we have been migrating away from Atmosphere package manager towards NPM. As we continue to migrate away, we may publish other NPM packages using rollup.

See more
Get Advice from developers at your company using Private StackShare. Sign up for Private StackShare.
Learn More
Pros of Browserify
Pros of Webpack
  • 75
    Node style browser code
  • 52
    Load modules installed by npm
  • 45
    Works great with gulp.js
  • 38
    NPM modules in the brower
  • 35
    Open source
  • 16
    Node streams
  • 1
    Easy setup
  • 308
    Most powerful bundler
  • 182
    Built-in dev server with livereload
  • 143
    Can handle all types of assets
  • 87
    Easy configuration
  • 21
    Laravel-mix
  • 4
    Overengineered, Underdeveloped
  • 2
    Makes it easy to bundle static assets
  • 2
    Webpack-Encore
  • 1
    Better support in Browser Dev-Tools
  • 1
    Redundant

Sign up to add or upvote prosMake informed product decisions

Cons of Browserify
Cons of Webpack
    Be the first to leave a con
    • 11
      Hard to configure
    • 2
      Spaghetti-Code out of the box
    • 2
      SystemJS integration is quite lackluster
    • 2
      Loader architecture is quite a mess (unreliable/buggy)
    • 2
      Fire and Forget mentality of Core-Developers
    • 2
      No clear direction

    Sign up to add or upvote consMake informed product decisions

    What is Browserify?

    Browserify lets you require('modules') in the browser by bundling up all of your dependencies.

    What is Webpack?

    A bundler for javascript and friends. Packs many modules into a few bundled assets. Code Splitting allows to load parts for the application on demand. Through "loaders" modules can be CommonJs, AMD, ES6 modules, CSS, Images, JSON, Coffeescript, LESS, ... and your custom stuff.

    Need advice about which tool to choose?Ask the StackShare community!

    What companies use Browserify?
    What companies use Webpack?
    See which teams inside your own company are using Browserify or Webpack.
    Sign up for Private StackShareLearn More

    Sign up to get full access to all the companiesMake informed product decisions

    What tools integrate with Browserify?
    What tools integrate with Webpack?

    Sign up to get full access to all the tool integrationsMake informed product decisions

    Blog Posts

    What are some alternatives to Browserify and Webpack?
    Bower
    Bower is a package manager for the web. It offers a generic, unopinionated solution to the problem of front-end package management, while exposing the package dependency model via an API that can be consumed by a more opinionated build stack. There are no system wide dependencies, no dependencies are shared between different apps, and the dependency tree is flat.
    Babel
    Babel will turn your ES6+ code into ES5 friendly code, so you can start using it right now without waiting for browser support.
    rollup
    It is a module bundler for JavaScript which compiles small pieces of code into something larger and more complex, such as a library or application. It uses the new standardized format for code modules included in the ES6 revision of JavaScript, instead of previous idiosyncratic solutions such as CommonJS and AMD.
    RequireJS
    RequireJS loads plain JavaScript files as well as more defined modules. It is optimized for in-browser use, including in a Web Worker, but it can be used in other JavaScript environments, like Rhino and Node. It implements the Asynchronous Module API. Using a modular script loader like RequireJS will improve the speed and quality of your code.
    Parcel
    Parcel is a web application bundler, differentiated by its developer experience. It offers blazing fast performance utilizing multicore processing, and requires zero configuration.
    See all alternatives