feat(nf): Use es module shims fully instead of global cache not in sync #517
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Split of #513
Description
For now, the importmap is only used for resolving the shared library. Adding the exposes to it does not change anything because a custom global cache is used to store the remotes and consumed by
loadRemote
.Then the
importShims
is used only to load an URL. It could be used with the key of the exposes likeimportShims('mfe1/Component')
and then the resolution of the URL is automatic.In this PR, I wanted to simplify by:
importShims('mfe1/Component')
like a javascript imports instead of using the baseUrl