Need advice about which tool to choose?Ask the StackShare community!
Add tool
Decisions about Browserify and rollup
Abigail Watson
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.
Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn MorePros of Browserify
Pros of rollup
Pros of Browserify
- Node style browser code75
- Load modules installed by npm52
- Works great with gulp.js45
- NPM modules in the brower38
- Open source34
- Node streams16
- Easy setup1
Pros of rollup
- Makes it easy to publish packages3
- Easier configuration3
- Better tree shaking2
- Provides smaller bundle size2
- Produces very clean code1
- Very reliable1
- Very robust Plugin-API (years old Plugins still work)1
- Very flexible1
- Was built with ESM-Modules in mind1
- Integrates seamlessly with SystemJS1
Sign up to add or upvote prosMake informed product decisions
Cons of Browserify
Cons of rollup
Cons of Browserify
Be the first to leave a con
Cons of rollup
- No clear path for static assets1
- No Loader like Webpack (need to use sjs or ESM imports)1
- Almost everything needs to be a Plugin1
- Manual Chunking is a bit buggy1
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 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.
Need advice about which tool to choose?Ask the StackShare community!
Jobs that mention Browserify and rollup as a desired skillset
What companies use Browserify?
What companies use rollup?
What companies use Browserify?
What companies use rollup?
See which teams inside your own company are using Browserify or rollup.
Sign up for StackShare EnterpriseLearn MoreSign up to get full access to all the companiesMake informed product decisions
What tools integrate with Browserify?
What tools integrate with rollup?
What tools integrate with rollup?
Blog Posts
What are some alternatives to Browserify and rollup?
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.
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.
Babel
Babel will turn your ES6+ code into ES5 friendly code, so you can start using it right now without waiting for browser support.
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.