Page refresh required to reflect changes about import-map-overrides HOT 2 CLOSED

Hi @HemTech, good question. The import maps spec strictly forbids this behavior (docs):

As another consequence of how import maps affect all imports, attempting to add a new <script type="importmap"> after any module graph fetching has started is an error. The import map will be ignored, and the <script> element will fire an error event.

Contrary to the spec, SystemJS provides a few APIs that support modifying the module registry without reloading the page. Specifically, System.delete plus a subsequent System.import() will cause the module to be downloaded again.

Additionally, in the last several days, SystemJS has considered deviating from the spec to allow for direct import map updates. See systemjs/systemjs#2215, systemjs/systemjs#2211, and https://github.com/guybedford/import-maps-extensions.

I'm open to this feature being added to import-map-overrides, but there are a few edge cases that might become tricky, as this is essentially hot reloading of modules. One question for you - are you using import-map-overrides for local development purposes, or for managing deployments? I would strongly discourage using it as a deployment mechanism.

from import-map-overrides.

This issue seems to be stale. With the current vision about moving towards ESM, I believe we can close it, for the time being. @HemTech, please, feel free to add comments in case you want it to be reopened.

from import-map-overrides.