import.meta.resolve no longer available in loaders >= v20

[halfmatthalfcat]

Version

20.0.0

Platform

Darwin ....* 21.5.0 Darwin Kernel Version 21.5.0: Tue Apr 26 21:08:22 PDT 2022; root:xnu-8020.121.3~4/RELEASE_X86_64 x86_64

Subsystem

No response

What steps will reproduce the bug?

package.json

{
  "name": "import-meta-resolve-test",
  "type": "module"
}

loader.mjs

export function load(url, _, next) {
  console.log(import.meta.resolve);
  return next(url);
}

index.mjs

console.log("hello world");

---

node --experimental-import-meta-resolve --experimental-loader ./loader.mjs ./index.mjs

How often does it reproduce? Is there a required condition?

• Must be on Node v20 or above
• Reproduced every time

What is the expected behavior? Why is that the expected behavior?

console.log in loader should resolve import.meta.resolve

What do you see instead?

undefined is printed

Additional information

import.meta.resolve exists in <= Node v20, at least I checked in 16-19.

I didn't see anywhere in 20+ release notes of this capability being removed. If this is known, feel free to close this.

[atlowChemi]

@nodejs/loaders cc

[aduh95]

Yes it's a known limitation, import.meta.resolve returns a string synchronously, however the resolve hook chain is async, so it can onl y be exposed on the main thread. We have considered to expose it on the loader thread but returning a promise instead of a string, but it was deemed too confusing so not worth it. We could consider expose a different utils that does the same thing but asynchronously.

[GeoffreyBooth]

If it’s not documented yet then we should at least mention it in the docs, with any workarounds if there are any.

[aduh95]

Would you like to send a PR?

[GeoffreyBooth]

Would you like to send a PR?

@aduh95 I don’t know who you’re addressing this to. I asked about possible workarounds in https://openjs-foundation.slack.com/archives/C053UCCP940/p1692289284713799.