What is the best alternative to rollup?

Question

Help millions of people make better decisions.

Each month, over 2.8 million people use Slant to find the best products and share their knowledge. Pick the tags you’re passionate about to get a personalized feed and begin contributing your knowledge.

score 11 · Answer 1

stealjs

Top Pro

Supports several modules types

StealJS has support for AMD, CJS and ES6 module types. See More

Top Con

Changing the order of require statements causes unexpected behavior

Sometimes changing the order of the require statements in a JavaScript file loaded with stealjs may cause unexpected problems or even breaking the code altogether. See More

Top Pro

Support for LESS and CSS

StealJS can also load CSS and LESS files in addition to JavaScript modules. See More

Top Pro

Mix ES6 AMD and CommonJS

StealJS supports using all three module types, even in the same file. See More

Top Pro

ES6 module support

StealJs supports ES6 modules and their import and export methods without having to compile them to CommonJS require. See More

Top Pro

Support for ES6

StealJS supports transpiling of ES6 code to ES5 See More

Top Pro

Supports all systemjs based plugins

Top Pro

Supports source maps for easier debugging

Source maps allow for easier debugging, because they allow you to find the problems within the origin files instead of the output file. See More

Top Pro

Share the same modules client-side and server-side

Because StealJS allows you to use the same require() function as node.js, you can easily share modules between the client-side and server-side. See More

Top Pro

Tap into npm's huge module ecosystem

Using StelaJS opens you up to npm, that has over 80k modules of which a great amount work both client-side and server-side. And the list is growing rapidly. See More

See All Experiences

11 0

score 37 · Answer 2

JSPM

Top Pro

Registry agnostic

JSPM is registry agnostic, it can pull packages from npm and github and is built in such a way it can support more. See More

Top Con

You need to be an expert to write shims

You can load any module. But that comes with the price: you need to find or write configs to load a particular rare module. See More

Top Pro

Switch between async or sync load

With a simple command you could change between load the modules async by systemjs or sync with a bundle file. See More

Top Con

Watcher has bugs

Watching would benefit from improvements See More

Top Pro

Much faster than Webpack or Browserify

While Webpack and Browserify recompile the source code using Babel, jspm is the only packager that can load prebuild/minified code downloaded from the npm registry. See More

Top Con

Unstable API

0.17 is still in beta. 0.16 is lacking features. See More

Top Pro

Easy install packages from npm, github or any git repository

Top Con

Poor bundler performance

Bundling performance is slow, though offset by the fact that bundling is not required during development, since it can load dependencies asynchronously. See More

Top Pro

Versioned package urls

It creates a packages folders which are versioned. This makes it future proof for a time where we stop bundling all the code. In the following presentation Guy Bedford calls bundling an anti-pattern. See More

Top Con

Doesn't hide complexity

JSPM doesn't try to hide complexity from the user. I.e. when some issue emerges you need understand a lot to be able to patch it or create a workaround. See More

Top Pro

Module style agnostic

Loads ES6, AMD, CommonJS and globals. See More

Top Pro

Can transcompile ES6, JSX and Typescript

Top Pro

Bundled based on imported modules without any config

Create the bundle file without config and add only the modules imported. See More

Top Pro

Very easy to start with

See All Experiences

37 8

score 84 · Answer 3

Webpack

Top Pro

Rich and flexible plugin infrastructure

Plugins and loaders are easy to write and allow you to control each step of the build, from loading and compiling CoffeeScript, LESS and JADE files to smart post processing and asset manifest building. See More

Top Con

Config file may be hard to understand

Due to a somewhat hard to grasp syntax, configuring Webpack may take some time. See More

Top Pro

Tap into npm's huge module ecosystem

Using Webpack opens you up to npm, that has over 80k modules of which a great amount work both client-side and server-side. And the list is growing rapidly. See More

Top Con

Can not load files discovered during runtime

Top Pro

ES6 module support

Webpack supports ES6 modules and their import and export methods without having to compile them to CommonJS require See More

Top Pro

Can create a single bundle or multiple chunks loaded on demand, to reduce initial loading time

Webpack allows you to split your codebase into multiple chunks. Chunks are loaded on demand. This reduces the initial loading time. See More

Top Pro

Supports source maps for easier debugging

Source maps allow for easier debugging, because they allow you to find the problems within the origin files instead of the output file. See More

Top Pro

Share the same modules client-side and server-side

Because Webpack allows you to use the same require() function as node.js, you can easily share modules between the client-side and server-side. See More

Top Pro

Bundles CommonJs and AMD modules (even combined)

Webpack supports AMD and CommonJS module styles. It performs clever static analysis on the AST of your code. It even has an evaluation engine to evaluate simple expressions. This allows you to support most existing libraries. See More

Top Pro

Mix ES6 AMD and CommonJS

Webpack supports using all three module types, even in the same file. See More

Top Pro

Limit plugin integration issues

See All Experiences

84 16

score 44 · Answer 4

RequireJS

Top Pro

Works with basically every desktop browser, even IE6

RequireJS supports IE6+, FF2+, Safari3.2+, Chrome3+ & Opera 10+. See More

Top Con

On its way out

Latest stable release is 2 months old with little development occurring on Github. See More

Top Pro

Has a RequireJS optimizer

After building all the modules to be loaded, the built files can be optimized as well (minified and concatenated), even though this is a completely optional step, but doing so could be a lot beneficial for your site's performance. See More

Top Con

Poor handling of circular references

If you create a circular reference between two files, it will typically quietly break - the reference on one side will end up undefined. See More

Top Pro

Supports nested dependencies

If your project has nested dependencies, you won't have to worry about resolving them at all. Because RequireJS will do that for you. See More

Top Con

AMD spec uses globals

The global ‘require’ and ‘define’ methods make namespace collisions likely if building a 3rd party plugin. AMD loaders line require are best if you control the site. See More

Top Pro

Well tested

Since the RequireJS is quite popular among the dev community, that automatically means that problems get sorted out very quickly and most of the core code has already been tested. See More

Top Con

Can't handle CSS dependencies

Top Pro

Well documented

The RequireJS module loader is extremely well documented. So no matter whether you're a pro at JS based web development or just a newbie, you will find the documentation very helpful whenever you're stuck or just starting out. Everything is well-defined and logically placed in proper sections in a manner such that it is very easy to understand. See More

Top Pro

AMD & CJS support

While RequireJS is mainly an AMD implementation, it can, with rare exceptions, implement CJS as well. See More

Top Pro

You don't need a server to get started

One of the best advantages of RequireJS over Browserify is that you don't need a nodejs environment to get started. Just "require" your dependencies and it takes care of loading them. By contrast, Browserify requires a running NodeJS implementation so you can build your one monolithic file, then you can push the file to your static web server. See More

Top Pro

Always running site unbundled

With other loaders, aka browserify, it isn't possible to run your site without first bundling. Require.js can load everything async which is pretty powerful. See More

Top Pro

Simple

Because of its easy to understand documentation, the RequireJS module loader is super simple to use; module definitions are as easy as defining just a key/value pair. See More

Top Pro

Can load new modules without being recompiled

It's the one of the few modules in this category that can handle IOC-style dependency injection. The others work well for apps that have knowable dependency lists at compile time, but this is the only one that can load new modules without being recompiled. See More

Top Pro

Lazily-loaded JS can access already loaded modules by name

Yet its run-time is still competitive if not better than Webpack's at higher density levels of modules. See More

Top Pro

Supports hot RE-loading

Persistent console logging, generational statefulness, promotes stateless DOM development. See More

See All Experiences

44 25

score 2 · Answer 5

Qoopido.demand

Top Pro

Supports localStorage caching

Modules will get loaded via XHR/XDR and get cached in localStorage to prevent further requests which improves performance escpecially on mobile See More

Top Pro

Fallback URLs

Any type of dependency can have multiple URLs defined to be used as fallback. See More

Top Pro

Additional support for loading HTML, CSS, JSON, and text

Loading is dealt with via handlers that are themselves modules (dynamically loaded and cached). Qoopido.demand comes with support for its own module format built-in and offers handlers for css, json and text. Due to handlersbeing modules themselves it is really easy to write custom handlers. See More

Top Pro

Optional support for SRI (sub resource integrity)

Support for SHA256, 384 and 512 identity checks for all types of loaded modules was added in version 2.0.7 See More

Top Pro

Offers internal auto-bundling to reduce the number of requests

By taking advantage of auto-bundling, it means that demand itself will combine requests without the user having to manually define a bundle. See More

Top Pro

Supports sourcemaps

Top Pro

Optional lz-string compression of localStorage cache content

Cached modules can be optionally & automatically compressed with lz-string loading a plugin (included in the distribution) either globally or on a per module or even per path/part of path base. See More

Top Pro

Per module setting of cache parameters

Version 1.1.2 of Qoopido.demand adds the possibility to not only set global caching parameters valid for all modules but allows for fine grained cache control on a per module basis. See More

Top Pro

Can load new modules without being recompiled

It's the one of the few modules in this category that can handle IOC-style dependency injection. The others work well for apps that have knowable dependency lists at compile time, but this is one of the few that can load new modules without being recompiled. See More

Top Pro

Optional cookie support to communicate module caching state to the server

Cookie support within Qoopido.demand can be enabled globally or per module. Whenever the localStorage cache for a module changes an accompanying cookie gets updated/deleted so the server can handle the clients module caching state and, e.g., inline modules as long as the client das not have them in localStorage. See More

Top Pro

Supports loading of non-module scripts

Qoopido.demand offers loading of legacy scripts as if they were modules through probe functions. These probe functions are similiar to Require.js shim, but where shim allows only string parameters, Qoopido.demand's probes are JavaScript functions that can check whatever you want. See More

Top Pro

Promise like interface

Although not depending on native promise support it offers a promise like interface which greatly improves readability of code See More

Top Pro

Supports nested dependencies

Dynamically loaded modules can have further dependencies that will get dynamically resolved and loaded See More

Top Pro

localStorage caching removes the need to bundle

It enables and encourages the development of atomic modules that do not necessarily have to get bundled (manually or via build-process) to gain performance See More

Top Pro

Support for legacy browsers

Qoopido.demand has recently added support for legacy browsers. Including IE8. See More

Top Pro

Supports loading of bundles

From version 1.1.1 onwards Qoopido.demand is able to load multiple concatenated modules in a single request (like jsdelivr) while maintaining automatic module resolution. See More

See All Experiences

2 0

score 18 · Answer 6

Brunch

Top Pro

Compilation is super fast

According to speed benchmarks, Brunch is one of the fastest tools around for compiling files. According to the authors of Brunch the reason behind this speed is that it recompiles only the changes that were made to an app and performs extensive caching of the app's code. See More

Top Pro

Time to setup is extremely low

After installing Brunch the next step is to load a skeleton from git.io/skeletons. This step is as easy as installing another plugin from the npm registry, just point Brunch to the path of the required skeleton/generator then wait for it to work out its magic. Next, run brunch build then wait for a second or two and voila! the project is ready. See More

Top Pro

The configuration file is small and the configuration itself is fast and easy

Brunch's config files can be extremely small compared to other alternatives. The fact that brunch also allows you to chose from a number of generators also lowers the configuration time considerably. See More

Top Pro

Concatenates scripts and styles and auto-generates matching source maps

Brunch automatically produces a source map for all javascript files and CSS stylesheets whenever it minifies an app's resources. This little feature is extremely helpful when debugging is required at the client end. See More

Specs

Number of Plugins:~100

Processing method:Pipeline

Task instruction style:Code

18 3

score 1 · Answer 7

module-concat

Top Pro

Supports Client-side Browser Projects

Provides some support for concatenating client-side browser JavaScript modules. Also, can process the browser property in package.json. See More

Top Con

Not a full-featured bundler

This doesn't handle CSS or HTML stuff. It only bundles JavaScript files. See More

Top Pro

Supports languages that compile to JS

For example, CoffeeScript is supported using the compilers option. See More

Top Pro

Lightweight

This library just concatenates CommonJS modules together into a single *.js file. Nothing else. It only uses 1 dependency: resolve See More

1 0

score 10 · Answer 8

SystemJS

Top Pro

Supports multiple module formats

SystemJS supports AMD, CommonJS and ES6 modules. See More

Top Pro

Can load static assets through plugins

System.js supports loading static assets such as images or stylesheets through loader plugins. See More

Top Pro

No tools needed in dev, can seamlessly bundle when moving to prod

Top Pro

Concise, Granular Configuration

Top Pro

Easy to migrate to

A migration from RequireJS + loadCSS to only SystemJS can be done in only 2.5 hours. See More

Top Pro

Even its dev. build is smaller than most of its competitors prod. build

With ~15Kb, its development build can load almost any type of JS module. See More

10 6

score 1 · Answer 9

Curl.js

Top Pro

Size ~4KB (gzipped)

Top Con

Development has stopped

The maintainers have announced that all development for CurlJS has stopped, at least for the foreseeable future. See More

Top Pro

Async loading on demand

Async loading on demand including loadings from cdns. For example it is easy to load jquery from cdn as a module. The same thing is not that easy to achieve in Webpack See More

Top Pro

Provides legacy loader

Legacy loader supports loading of plain js files and exporting globals or even expressions. See More

Top Pro

AMD & CJS module support

Supports both AMD and CommonJS modules. See More

1 1

score 1 · Answer 10

Gourmet

Top Con

Feature set is unclear

Top Pro

Friendly asset handling

Auto-asset inclusion, native CSS support, and flexible bundling make handling your assets simple. See More

Top Con

Not available yet

Top Pro

ES6 support

Supports ES6 syntax by default. See More

Top Con

Zero documentation

Top Pro

Easy configuration

Declarative configuration makes project setup easy. See More

Top Con

Browser support unknown

Top Pro

Isomorphic rendering by default

The runtime environment allows for isomorphic rendering of React applications by default. See More

See All Experiences

1 4