Guy Bedford

You need to be using `with` here and that should make the difference - ie it shouldn't work in Chrome 123. That is, we don't currently support rewriting the `with`...

Yes that's the check we do today, it just means that browsers that only support `assert` but not `with` won't utilize native CSS and JSON module support in es-module-shims. Adding...

@mangelozzi CSS modules need to still be explicitly enabled for polyfilling via the `polyfillEnable` feature: ```html { "polyfillEnable": ["css-modules", "json-modules", "wasm-modules"] } ```

The function is supposed to be synchronous if you've awaited init, but if you haven't awaited init it should be async. I think this was changed in the TypeScript migration....

Thanks for sharing. There is actually a hot reload implementation for this project in https://github.com/guybedford/es-module-shims/pull/269, I just never landed it (not sure why... it works fine!). The main issue is...

Are you writing a custom plugin here? It would help to know how you are triggering the path to begin with. The `parentUrl` should never be a blob URL for...

Yes that is correct, blobs do not support relative resolution, so you need to work around that. This is not really a limitation of this project though, since `new URL('/path',...

URLs are resolved to the parent - in this case the parent **is** a blob URL. If you try to do `import('blob:...')` where that blob imports from `/asdf`, it will...

I agree that if anything the fix would be to provide a clearer more aligned error message.

If anything, import maps force you to see what you're loading instead of having an invisible bundle. And they don't solve dependency bloat any other way than making it apparent....