SystemJS

Configurable module loader enabling backwards compatibility workflows for ES modules in browsers. If you're interested in modern workflows for ES module compatible browsers only, see ES Module Shims.

Release Links:

For discussion, join the Gitter Room.

Examples

The systemjs-examples repo contains a variety of examples demonstrating how to use SystemJS.

Performance

SystemJS can load multiple modules in less than a millisecond with its performance around a factor of 1.5 times the performance of native ES modules. The following performance benchmark was run by loading 426 javascript modules (all of @babel/core) on a Macbook pro with fast wifi internet connection. Each test was the average of five page loads in Chrome 80.

Tool	Uncached	Cached
Native modules	1668ms	49ms
SystemJS	2334ms	81ms
es-module-shims	2671ms	602ms

Overview

Introduction video

SystemJS provides two hookable base builds:

1. s.js minimal loader

The minimal 2.3KB s.js loader provides a workflow where code written for production workflows of native ES modules in browsers (like Rollup code-splitting builds), can be transpiled to the System.register module format to work in older browsers that don't support native modules, including IE11++.

Since the ES module semantics such as live bindings, circular references, contextual metadata, dynamic import and top-level await can all be fully supported this way, while supporting CSP and cross-origin support, this workflow can be relied upon as a polyfill-like path.

Support for loading bare specifier names through import maps (formerly package maps, formerly map configuration), loaded via <script type="systemjs-importmap"> (requires a fetch polyfill for eg IE11).
Loads and resolves modules as URLs, throwing for bare specifier names (eg import 'lodash') like the native module loader.
Loads System.register modules.
Core hookable extensible loader supporting custom extensions.

2. system.js loader

The 3.7KB system.js loader loader builds on the s.js core and adds support for global loading, non-javascript module, and the SystemJS registry API.

Support for loading bare specifier names through import maps (formerly package maps, formerly map configuration), loaded via <script type="systemjs-importmap"> (requires a fetch polyfill for eg IE11).
Includes the global loading extra for loading global scripts, useful for loading library dependencies traditionally loaded with script tags.
Tracing hooks and registry deletion API for reloading workflows.
Supports loading Wasm, CSS and JSON module types.

3. system-node.cjs loader

The system-node.cjs loader is a version of SystemJS build designed to run in Node.js, typically for workflows where System modules need to be executed on the server like SSR. It has the following features:

Loading System modules from disk (via file:// urls).
Loading System modules from network (via http:// urls), with included caching that respects the Content-Type header.
Loading global modules with the included global loading extra
Supports loading Wasm, CSS and JSON module types.
Import Maps (via the applyImportMap api).
Tracing hooks and registry deletion API for reloading workflows.

Loading CommonJS modules is not currently supported in this loader and likely won't be. If you find you need them it is more advisable to use Node.js native module support where possible instead of the SystemJS Node.js loader.

Extras

The following pluggable extras can be dropped in with either the s.js or system.js loader:

AMD loading support (through Window.define which is created).
Named exports convenience extension support for global and AMD module formats (import { x } from './global.js' instead of import G from './global.js'; G.x)
Named register supports System.register('name', ...) named bundles which can then be imported as System.import('name') (as well as AMD named define support)
Transform loader support, using fetch and eval, supporting a hookable loader.transform

The following extras are included in system.js loader by default, and can be added to the s.js loader for a smaller tailored footprint:

Global loading support for loading global scripts and detecting the defined global as the default export. Useful for loading common library scripts from CDN like System.import('//unpkg.com/lodash').
Module Types .css, .wasm, .json module type loading support in line with the existing modules specifications.

Since all loader features are hookable, custom extensions can be easily made following the same approach as the bundled extras. See the hooks documentation for more information.

Backers

Thank you to all our backers! 🙏 [Become a backer]

Installation

npm install systemjs

Documentation

Example Usage

Loading a System.register module

You can load System.register modules with a script element in your HTML:

<script src="system.js"></script>
<script>System.import('/js/main.js')</script>
<script>System.import('name-of-module')</script>

Loading with System.import

You can also dynamically load modules at any time with System.import():

System.import('/js/main.js');

where main.js is a module available in the System.register module format.

Bundling workflow

For an example of a bundling workflow, see the Rollup Code Splitting starter project - https://github.com/rollup/rollup-starter-code-splitting.

Note that when building System modules you typically want to ensure anonymous System.register statements like:

System.register([], function () { ... });

are emitted, as these can be loaded in a way that behaves the same as normal ES modules, and not named register statements like:

System.register('name', [], function () { ... });

While these can be supported with the named register extension, this approach is typically not recommended for modern modules workflows.

Import Maps

Say main.js depends on loading 'lodash', then we can define an import map:

<script src="system.js"></script>
<script type="systemjs-importmap">
{
  "imports": {
    "lodash": "https://unpkg.com/lodash@4.17.10/lodash.js"
  }
}
</script>
<!-- Alternatively:
<script type="systemjs-importmap" src="path/to/map.json">
-->
<script>
  System.import('/js/main.js');
</script>

Community Projects

A list of projects that use or work with SystemJS in providing modular browser workflows. Post a PR.

es-dev-server - A web server for developing without a build step.
import map overrides - Dynamically inject an import map stored in local storage so that you can override the URL for any module. Can be useful for running development modules on localhost against the server.
js-env - Collection of development tools providing a unified workflow to write JavaScript for the web, node.js or both at the same time.
jspm.org - Package manager for native modules, using SystemJS for backwards compatibility.
single-spa - JavaScript framework for front-end microservices.
systemjs-webpack-interop - npm lib for setting webpack public path and creating webpack configs that work well with SystemJS.
esm-bundle - list of System.register versions for major libraries, including documentation on how to create a System.register bundle for any npm package.

Loader Extensions

This list can be extended to include third-party loader extensions. Post a PR.

transform-babel Supports ES module transformation into System.register with Babel.
systemjs-css-extra CSS loader plugin

Compatibility with Webpack

Code-splitting builds on top of native ES modules, like Rollup offers, are an alternative to the Webpack-style chunking approach - offering a way to utilize the native module loader for loading shared and dynamic chunks instead of using a custom registry and loader as Webpack bundles include. Scope-level optimizations can be performed on ES modules when they are combined, while ensuring no duplicate code is loaded through dynamic loading and code-sharing in the module registry, using the features of the native module loader and its dynamic runtime nature.

systemjs-webpack-interop is a community-maintained npm library that might help you get webpack and systemjs working well together.

As of webpack@4.30.0, it is now possible to compile webpack bundles to System.register format, by modifying your webpack config:

{
  output: {
    libraryTarget: 'system', 
  }
}

If building code using the System global in Webpack, the following config is needed to avoid rewriting:

{
  module: {
    rules: [
      { parser: { system: false } }
    ]
  }
}

Using npm packages

Third party libraries and npm packages may be used as long as they are published in a supported module format. For packages that do not exist in a supported module format, here is a list of github repos that publish System.register versions of popular third party libraries (such as react, react-dom, rxjs, etc).

Polyfills for Older Browsers

Promises

Both builds of SystemJS need Promises in the environment to work, which aren't supported in older browsers like IE11.

Promises can be conditionally polyfilled using, for example, Bluebird (generally the fastest Promise polyfill):

<script>
  if (typeof Promise === 'undefined')
    document.write('<script src="node_modules/bluebird/js/browser/bluebird.core.js"><\/script>');
</script>

Generally document.write is not recommended when writing web applications, but for this use case it works really well and will only apply in older browsers anyway.

Fetch

To support import maps in the system.js build, a fetch polyfill is need. The GitHub polyfill is recommended:

<script>
  if (typeof fetch === 'undefined')
    document.write('<script src="node_modules/whatwg-fetch/fetch.js"><\/script>');
</script>

Constructable Stylesheets

If using CSS modules, a Constructable Stylesheets polyfill is needed - see the module types documentation for further info.

Contributing to SystemJS

Project bug fixes and changes are welcome for discussion, provided the project footprint remains minimal.

To run the tests:

npm run build && npm run test

Changes

For the changelog, see CHANGELOG.md.

License

MIT

lesnicaaa/systemjs