Motivation
If I'm not mistaken, the HTML spec doesn't disallow the use of multiple import map scripts in a document. This means that it is conceivable that an HTML document may have more import maps than the one created by merging overridable import maps.
If this is the case then the vite-aim plug-in is probably interested in knowing them for auto-externalization purposes.
Yes, a CollageJS project should only contain overridable import maps. After all, one can only add import maps while in Vite serve mode using a plug-in. However, since it is this package's intention to work outside the CollageJS boundary, one never knows if a project out there may be doing extra import maps.
Proposal
Just for transmission purposes, merge the resultant import map with any additional import maps in the document's HEAD element.
Motivation
If I'm not mistaken, the HTML spec doesn't disallow the use of multiple import map scripts in a document. This means that it is conceivable that an HTML document may have more import maps than the one created by merging overridable import maps.
If this is the case then the
vite-aimplug-in is probably interested in knowing them for auto-externalization purposes.Yes, a CollageJS project should only contain overridable import maps. After all, one can only add import maps while in Vite
servemode using a plug-in. However, since it is this package's intention to work outside the CollageJS boundary, one never knows if a project out there may be doing extra import maps.Proposal
Just for transmission purposes, merge the resultant import map with any additional import maps in the document's HEAD element.