You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 13, 2020. It is now read-only.
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
The text was updated successfully, but these errors were encountered:
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 freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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
The text was updated successfully, but these errors were encountered: