Clarify where the base is for relative module specifiers

[sapphi-red]

MDN URL

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/import#module-name

What specific section or headline is this issue about?

Syntax > module-name

What information was incorrect, unhelpful, or incomplete?

When a relative path is written, it does not say where the base will be at resolution.

What did you expect to see?

Update This is often a relative or absolute URL to the .js file containing the module. to This is often an URL relative to the file containing the statement or an absolute URL pointing the .js file containing the module..
I'm not sure if this wording is clear though.

Import maps might need to be taken into consideration.

Do you have any supporting links, references, or citations?

• HTML Standard: https://html.spec.whatwg.org/multipage/webappapis.html#integration-with-the-javascript-module-system:resolve-a-module-specifier:~:text=The%20specifier%20will%20be%20resolved%20relative%20to%20the%20active%20script
• The fetch page explains where the base is (albeit with different value): https://developer.mozilla.org/en-US/docs/Web/API/Window/fetch#resource:~:text=The%20URL%20may%20be%20relative%20to%20the%20base%20URL%2C%20which%20is%20the%20document%27s%20baseURI%20in%20a%20window%20context%2C%20or%20WorkerGlobalScope.location%20in%20a%20worker%20context

Do you have anything more you want to share?

Another page that should be updated together.

• https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/import#modulename

[Josh-Cena]

We try not to bias our module documentation to the web, as the module specifier resolution can differ between environments. Nevertheless, I like your suggestion, and if we prefix it by "in the browser" we can certainly add it to the docs (linking to the import map docs).