Import maps #146
Request for Mozilla Position on an Emerging Web Specification
(It doesn't really feel like a primitive however as it's not necessarily available before the first fetch (e.g., one from a
referenced this issue
Mar 14, 2019
I think this is a bit strong :). Here's how I see it, referencing implementation staging notes in the explainer:
I apologize for this context being spread out throughout a few documents, plus in my head. I am hoping to get a real spec for at least stage 1 over the next week or two. But hopefully this helps explain why I don't think it's as fundamental of a change as all that.
I agree with your assessment that it's not a primitive. It's mainly a way of (a) controlling "resolve a module specifier; (b) via
(Not a Mozillian, but @annevk suggested I comment here.)
Overall, I like the import maps proposal. I think it does a good job of meeting its stated goals, and could be a good basis future mechanisms for more detailed declarative ways to invoke polyfills (c.f. whatwg/html#4432).
Some issues with active discussion from web developers about whether the goals of import maps are sufficient for their use cases:
Some of these features might be possible to add in follow-on proposals; the concern has been raised that the ability to remap non-bare specifiers might interfere with some future options.