Reference for stage 3 source-phase-imports

[Josh-Cena]

Part of #44475

[github-actions]

Preview URLs (11 pages)

• /en-US/docs/Web/JavaScript/Reference/Global_Objects/AbstractModuleSource
• /en-US/docs/Web/JavaScript/Reference/Global_Objects
• /en-US/docs/Web/JavaScript/Reference/Operators/import/source
• /en-US/docs/Web/JavaScript/Reference/Operators/import
• /en-US/docs/Web/JavaScript/Reference/Operators
• /en-US/docs/Web/JavaScript/Reference/Statements/export
• /en-US/docs/Web/JavaScript/Reference/Statements/import/source
• /en-US/docs/Web/JavaScript/Reference/Statements/import/with
• /en-US/docs/Web/JavaScript/Reference/Statements/import
• /en-US/docs/Web/JavaScript/Reference
• /en-US/docs/WebAssembly/Reference/JavaScript_interface/Module

Flaws (10)

Note! 8 documents with no flaws that don't need to be listed. 🎉

Found an unexpected or unresolvable flaw? Please report it here.

URL: /en-US/docs/Web/JavaScript/Reference
Title: JavaScript reference
Flaw count: 4

• macros:
  • Macro jsxref produces link /en-US/docs/Web/JavaScript/Reference/this which is a redirect
  • Macro jsxref produces link /en-US/docs/Web/JavaScript/Reference/new which is a redirect
  • Macro jsxref produces link /en-US/docs/Web/JavaScript/Reference/delete which is a redirect
  • Macro jsxref produces link /en-US/docs/Web/JavaScript/Reference/instanceof which is a redirect

---

URL: /en-US/docs/Web/JavaScript/Reference/Global_Objects
Title: Standard built-in objects
Flaw count: 1

• macros:
  • Macro jsxref produces link /en-US/docs/Web/JavaScript/Reference/this which is a redirect

---

URL: /en-US/docs/Web/JavaScript/Reference/Operators
Title: Expressions and operators
Flaw count: 5

• macros:
  • Macro jsxref produces link /en-US/docs/Web/JavaScript/Reference/this which is a redirect
  • Macro jsxref produces link /en-US/docs/Web/JavaScript/Reference/new which is a redirect
  • Macro jsxref produces link /en-US/docs/Web/JavaScript/Reference/new which is a redirect
  • Macro jsxref produces link /en-US/docs/Web/JavaScript/Reference/delete which is a redirect
  • Macro jsxref produces link /en-US/docs/Web/JavaScript/Reference/instanceof which is a redirect

External URLs (3)

URL: /en-US/docs/Web/JavaScript/Reference/Global_Objects/AbstractModuleSource
Title: AbstractModuleSource

• https://github.com/tc39/proposal-esm-phase-imports (1 time) (Note! This may be a new URL 👀)

---

URL: /en-US/docs/Web/JavaScript/Reference/Operators/import/source
Title: import.source()

• https://github.com/tc39/proposal-esm-phase-imports (1 time) (Note! This may be a new URL 👀)

---

URL: /en-US/docs/Web/JavaScript/Reference/Statements/import/source
Title: import source

• https://github.com/tc39/proposal-esm-phase-imports (1 time) (Note! This may be a new URL 👀)

(comment last updated: 2026-07-22 12:14:10)

[hamishwillee]

FYI @Josh-Cena In case you didn't see the response from Dan, the syntax is supported but right now you can't actually import anything: the ability to import WASM modules is still behind a pref and not public on Chrome or FF

I'm not sure how that affects rollout of this doc

[Josh-Cena]

If the only thing shipped is parsing and there's no valid use case, then I'd not document that at all at this point, or point out that the WASM source capability does exist but is behind a pref. In either case, it wouldn't change what I have written a great deal as I'd still pretend that WASM source capability exists.

[hamishwillee]

Fair enough. Given there is a behind pref implementation, its going to appear at some point.

[Josh-Cena]

I had a tiny obstacle. I will come back to this in less than a week, hoping that obstacle gets unblocked soon.

[hamishwillee]

Hi @Josh-Cena

So where are we with timing for this now? If we want these docs in then I think I should update BCD with the support for WASM modules behind a pref. It isn't really "ready for testing" IMO, but this would allow us to make it clear that nothing supports the feature in the wild.

Either way, ping me when you're wanting a new review.

[Josh-Cena]

Yeah I'm mostly done; the only thing lacking is examples, which I'm not sure if I should have if the feature isn't actually useful (because, above all else, I can't actually test it). I'm not even sure if any documentation is necessary if it's not practically usable anywhere. But BCD should definitely be added anyway to record whatever the support status is. I'll leave the judgment call to you.

[hamishwillee]

Yeah I'm mostly done; the only thing lacking is examples, which I'm not sure if I should have if the feature isn't actually useful (because, above all else, I can't actually test it). I'm not even sure if any documentation is necessary if it's not practically usable anywhere. But BCD should definitely be added anyway to record whatever the support status is. I'll leave the judgment call to you.

Thanks @Josh-Cena . I've added BCD in mdn/browser-compat-data#30136

I'm conflicted about progressing these docs. There's a link to them in the release note that will remain unfulfilled, so it would suit me to have them in. But objectively it is confusing to talk about a feature that doesn't exist yet. I also think we should have examples, but there is no point until it is testable.

If it is up to me I propose you get this as far as you can, leave it in draft, and we wait until this has progressed enough for examples to be written before merging.

[Josh-Cena]

I agree; leaving the links hanging in the release notes doesn't seem too bad at this point.