Motivation
I am willing to bet that a significant portion of micro-frontend-powered applications create micro-frontends that don't import other micro-frontends.
If this is the case, posting the import map to piece-only Vite dev servers might be unnecessary.
⚠️ It might still be necessary if the import map is needed to auto-externalize shared dependencies like the React runtime, or perhaps a router library, etc.
Proposal
Alter the logic that determines which Vite servers are to receive the import map to account for this new option. If the new option is set to true, then @collagejs/imo will only ever submit the import map to the document's origin and nowhere else.
Manual Posting
If #23 goes out before this one, then manual posting should ignore this option and simply post to whichever servers have been selected in the user interface.
Motivation
I am willing to bet that a significant portion of micro-frontend-powered applications create micro-frontends that don't import other micro-frontends.
If this is the case, posting the import map to piece-only Vite dev servers might be unnecessary.
Proposal
Alter the logic that determines which Vite servers are to receive the import map to account for this new option. If the new option is set to
true, then@collagejs/imowill only ever submit the import map to the document's origin and nowhere else.Manual Posting
If #23 goes out before this one, then manual posting should ignore this option and simply post to whichever servers have been selected in the user interface.