Repository navigation
Expose importMetaResolve(url, baseURL) from node:module, and stabilize it #61127
Description
What is the problem this feature will solve?
In Node.js based tools it's common to need to "resolve url X as if it were imported from module Y".
Node.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.
https://github.com/wooorm/import-meta-resolve is, for example, a library that is basically code copy&pasted 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.
What is the feature you are proposing to solve the problem?
Node.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.
It'd be great if Node.js could expose the two-args version as an export of node:module, something like
import { resolveModuleURL } from "node:module"`;
resolveModuleURL(url, parent);with resolveModuleURL(url, import.meta.url) being equivalent to import.meta.resolve(url).
What alternatives have you considered?
This is related to #55756, which implements a more complex/comprehensive API.
Activity
github-actions commentedon Jul 20, 2026
This issue has been marked as stale due to 90 days of inactivity.
It will be automatically closed in 30 days if no further activity occurs. If this is still relevant, please leave a comment or update it to keep it open.
nicolo-ribaudo commentedon Jul 20, 2026
Still wanting this!
romainmenke commentedon Jul 20, 2026
We have the same use case in Stylelint and also still want this feature
github-actions commentedon Oct 20, 2026
This issue has been marked as stale due to 90 days of inactivity.
It will be automatically closed in 30 days if no further activity occurs. If this is still relevant, please leave a comment or update it to keep it open.
romainmenke commentedon Oct 20, 2026
Not stale
thescientist13 commentedon Oct 21, 2026
Would also love to see this