Skip to content
This repository has been archived by the owner on Jul 13, 2020. It is now read-only.

future and esm interop #543

Open
pocesar opened this issue Mar 31, 2018 · 1 comment
Open

future and esm interop #543

pocesar opened this issue Mar 31, 2018 · 1 comment

Comments

@pocesar
Copy link

pocesar commented Mar 31, 2018

now that es modules are officially here, what is the future of ES Module Loader (and therefore, SystemJS and JSPM)? I've been using JSPM for a long time, since the 0.17 came around, but need to think forward on the current and future states of things

@guybedford
Copy link
Member

The future focus of the SystemJS project is on the production loader, which is a small loader supporting loading System.register modules, WASM, AMD and globals.

The idea then is that browsers that support ES modules are fine - but if you need to load other module formats, or support older browsers, using the SystemJS production loader can provide this experience.

Also Rollup integration with SystemJS has been a big focus - Rollup now supports the System module format, so that ES modules can be optimized with the new code splitting feature in Rollup and loaded with the SystemJS production loader alongside CDN resources - read https://rollupjs.org/guide/en#experimental-code-splitting for more info.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants