Jolyn

I put together some thoughts and a benchmark in this document about this topic: https://docs.google.com/document/d/1IxkNGRIUbvQ0P8Uig9jkFte5gACCn-Y9zO1P5acnE9s/edit#

One of my main points in that document: > External import maps can be controlled and cached separately from the HTML files that reference them, which allows for updating javascript...

For whatever it's worth, I agree that dynamically adding an import map in the browser is a very worthwhile feature. Even after initial module loading has begun. I think it...

This sounds similar to https://github.com/WICG/import-maps/issues/137.

Guy Bedford and I are currently creating a package called `tracemap` that will create import maps from package.json dependencies, recursing through your node_modules. First release will be soon. Additionally, for...

I maintain a project called `import-map-overrides`, which allows developers to dynamically inject an import map that overrides the default URLs for modules, as a local development flow: https://github.com/joeldenning/import-map-overrides

I also maintain a project called import-map-deployer, which is a server that is called from CIs to update external import maps. I've used it for production deployments for four years...

I think this might be the best place for checking in on FF - https://github.com/mozilla/standards-positions/issues/146

What part of kremling doesn't work, if you use preact-compat and alias `react` and `react-dom` inside of the webpack config?

What could kremling do differently to make it work with both? The library has to do `import React from 'react'` in order for jsx to work. Potentially we could publish...