This might be interesting as a feature request on Vitest (for example, Vitest recently supported import.meta.filename and dirname vitest-dev/vitest#5011).

However, I imagine it would be tricky to support this since I don't think it can just work like "disable import.meta transform". Note that the source code (unless it's externalized) will be executed by vm.runInThisContext (like eval), so genuine import.meta.resolve is not available, which needs to be aware of original source file.

So, Vitest probably requires implementing this based on the 2nd argument version of import.meta.resolve(..., parentURL), but this is only available with --experimental-import-meta-resolve flags, so we would need users to customize poolOptions.execArgv. Also, if it's intended to be used with custom loader, then --import ... also needs to be included in execArgv probably.

I think it would be helpful if you can provide more details on "I need NodeJS's built-in imprt.meta.resolve to work". For example,

• Is your use case only about Vitest and not Vite SSR?
• Do you use parentURL variant of import.meta.resolve?
• Do you intend to use only relative path (like import.meta.resolve("./some-file.js")) or also node_modules (like import.meta.resolve("some-module"))?
• Do you (or your library's user?) intend to use import.meta.resolve together with NodeJs's custom loaders (e.g. --import tsx/esm)? (polyfill https://github.com/wooorm/import-meta-resolve doesn't work for this use case)