René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Expose `importMetaResolve(url, baseURL)` from `node:module`, and stabilize it","articleBody":"### What is the problem this feature will solve?\n\nIn Node.js based tools it's common to need to \"resolve url X as if it were imported from module Y\".\n\nNode.js does not expose this as an API, even though it implements it. It only exposes \"resolve url X as if it were imported from this current module\", through `import.meta.resolve`.\n\nhttps://github.com/wooorm/import-meta-resolve is, for example, a library that is basically code copy\u0026pasted from this repository and published on npm. The annoying part is that, as Node.js resolution rules change, libraries need to change too, and you need to basically check which version of Node.js you are on to know which rules to apply.\n\n### What is the feature you are proposing to solve the problem?\n\nNode.js does have a solution to this: the version of `import.meta.resolve` that takes two arguments, gated behind a flag (`--experimental-import-meta-resolve`). The reason it's behind a flag is because it would be different from the `import.meta.resolve` implementation of browsers, that takes only one argument.\n\nIt'd be great if Node.js could expose the two-args version as an export of `node:module`, something like\n```js\nimport { resolveModuleURL } from \"node:module\"`;\n\nresolveModuleURL(url, parent);\n```\nwith `resolveModuleURL(url, import.meta.url)` being equivalent to `import.meta.resolve(url)`.\n\n### What alternatives have you considered?\n\nThis is related to https://github.com/nodejs/node/pull/55756, which implements a more complex/comprehensive API. ","author":{"url":"https://github.com/nicolo-ribaudo","@type":"Person","name":"nicolo-ribaudo"},"datePublished":"2025-12-19T14:48:11.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/61127/node/issues/61127"}