Skip to content
This repository has been archived by the owner on Feb 18, 2024. It is now read-only.

Transpiling NPM packages directly into the JSPM packages folder? #967

Open
oleersoy opened this issue Sep 1, 2016 · 3 comments
Open

Transpiling NPM packages directly into the JSPM packages folder? #967

oleersoy opened this issue Sep 1, 2016 · 3 comments

Comments

@oleersoy
Copy link

oleersoy commented Sep 1, 2016

Just wondering whether it is currently possible?

http://stackoverflow.com/questions/39274404/transpiling-npm-packages-directly-into-the-jspm-packages-folder

@pcwinters
Copy link

@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

@guybedford
Copy link
Member

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.

@oleersoy
Copy link
Author

oleersoy commented Sep 9, 2016

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 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

3 participants