-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Import maps #564
Comments
Oh, and just to be clear: this will be for web projects only. There is no package.json file, no dependency management, etc. |
It's been two years and I haven't gotten around to implementing this. There are a few reasons why;
I just get the vibe that this doesn't belong in ImportJS. At least not yet. So I'm closing this for now and might reopen in a couple of years 😄 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Brace for craziness.
Chrome released official support for import maps on March 1. There's a polyfill enabling this in all browsers which have support for ES modules. It would be awesome if importjs could understand these maps, download the specifications, and set up my imports for me.
Example:
Once an import map is defined (inline or in separate file), then it affects all named imports that happen after it.
https://github.com/WICG/import-maps
https://caniuse.com/import-maps
This is a tricky thing to implement to 100%. But I'm thinking I might give it a shot to at least get some partial support. Maybe have ImportJS look at one specific file for importmaps at startup and then ignore the rest.
Perhaps urls could be downloaded to a node_modules-like folder and let importjs do its things as usual from that point forwards.
The text was updated successfully, but these errors were encountered: