This is not how they are loaded: see the previous paragraph (script type = module)

I'm not sure what you mean; how would you suggest to change it?

The execution of checkout.js is due to the <script type="module"> generated

(it is explained just a couple of lines before in the page)

To be honest i'm not sure there is much to add in here

Oh, I see - I now changed it.

Reason for adding it: I was confused to still seeeverything in importmap. And that issue shows that others are confused too... ;-)

I do agree. Still, not a reason to reexplain what has been said a couple lines before, mixing two very different notions: the entrypoint called, and the composition of the importmap.

You're referring to this sentence, right?:

By passing both app and checkout, the importmap() function will output the importmap and also add a <script type="module"> tag that loads the app.js file and the checkout.js file.

What I'm missing (and didn't know since yesterday) is the fact that the importmap is just a map with shortcuts ofpossible imports, and seeing an entry there doesn't mean that it's actually loaded.

So what about splitting those two aspects (this one, and theparent() issue) to two separate paragraphs? I could come up with a suggestion, but I have a question here:

Each page can only have oneimportmap, so importmap() must be called exactly once.

Is the bolded "importmap" referring to<script type="importmap"> (i.e. is this some restriction of the HTML standard)? Or is it about Twig's{{ impormap() }}?
=>Who is forbidding to have multiple importmaps?