import-maps
import-maps copied to clipboard
WICG
How to control the behavior of JavaScript imports
One issue came up recently with using import maps in production workflows is that browser extensions that inject ES modules into the page will block further import maps in the...
As mentioned in ["A convention-based flat mapping"](https://github.com/WICG/import-maps#a-convention-based-flat-mapping), it'd be ideal to also support a way of doing a very simple package map for applications which are laid out ahead of...
I'd like to move forward with an integrity proposal in SystemJS and ES Module Shims as an extension of this specification. Would this repo be the right place to suggest...
It's unclear how to apply import maps to a worker. There are essentially three categories of approach I can think of: - The worker-creator specifies the import map, e.g. with...
Currently external import maps are specified here, but in Chrome these still give the error: ``` External import maps are not yet supported. ``` I think it could be useful...
It seems like injecting import maps into the page after the first load is explicitly prohibited here: > Similarly, attempting to add a new after any module graph fetching, or...
Hi, It's clear that the purpose of import-maps is to enable loading complete ESM modules in a browser context. My question is whether there is anything in import-maps that facilitates...
The biggest hassle I have so far with managing import maps by hand is that, depending on the install method, modules can be nested, or not. The issue: Sometimes I...
It can be annoying when using vanilla modules, and some library ships their code with extensionless specifiers. Some ways to solve the issue: - ask them to update their code...