Just to share a little bit of my web platform feature process..

Following some user-visible breakage related to importmaps (https://x.com/thommaskelly/status/1782535482720567687), a bunch of us at Shopify decided to try and improve their resilience with regards to ES module loading

Together with @jaffathecake we’ve put together a proposal doc https://docs.google.com/document/d/1J1SColgpcZoVjERs05HhhFivLmAySCCUT3rL4vT9XZg/edit?pli=1, ran it by the relevant folks, and got their thumbs-up on the general concept

Thomas Kelly (@thommaskelly) on X

Yo @shopify -- you broke the the theme editor experience for any themes using import maps today by prepending <script type="module"> tags at the top of <head> before the <script type="importmap"> Revert? 🙏

X (formerly Twitter)

For the last week or so i've been working on an HTML PR to enable multiple import maps per document: https://github.com/whatwg/html/pull/10528

Now that the PR iteration process feels like we’re almost there , I think it’s time to start prototyping and see that it all actually works in practice. So I created a mapping from the relevant spec concepts to Chromium code: https://docs.google.com/document/d/1O2OlzcSVWF-8mmXr_Nz0ryz5CUiETyzPydOViE_9WRs/edit

Dynamic import maps by yoavweiss · Pull Request #10528 · whatwg/html

Introduction Import maps in their current form provide multiple benefits to web developers. They enable them to avoid cache invalidation cascades, and to be able to work with more ergonomic bare mo...

GitHub
Next step - a prototype Chromium CL and web platform tests (most probably a “translation” of the spec examples into test cases) as well as sending out requests for positions on WebKit and Mozilla