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 Feb 18, 2024. It is now read-only.
@guybedford, I've spent a couple of days trying to figure out a workflow to make this happen as well. Ultimately, I think support is rather light on what view is the most exciting use-case: async module loading w/ HTTP/2 that does not perform in-browser transpilation
This is the principle that https://npm.jspm.io and https://github.jspm.io were both built to, but that idea isn't ready for prime time until browsers can optimize the request / execution cycle adequately. Bundling thus remains the focus of the projects, but the HTTP/2 workflows are still very much the end goal.
Another thing that is somewhat related is trimming library components such that only the pieces needed are placed in the JSPM folder and the rest is shaved off. For example if I'm using underscore.js, but only the each function, then ideally only this function makes it into the JSPM folder and the rest of the library, along with any transitive dependencies that the inert code references, are shaved off.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Just wondering whether it is currently possible?
http://stackoverflow.com/questions/39274404/transpiling-npm-packages-directly-into-the-jspm-packages-folder
The text was updated successfully, but these errors were encountered: