import.meta.resolve is broken in vite-node, despite working in node

[GauBen]

Describe the bug

Given an index.mjs file with the following line of code:

console.log(import.meta.resolve("./index.mjs"));

It works properly when running node index.mjs, but throws an error when running in vite-node npx vite-node index.mjs: TypeError: __vite_ssr_import_meta__.resolve is not a function

Reproduction

1. mkdir repro && cd $_
2. echo 'console.log(import.meta.resolve("./index.mjs"));' > index.mjs
3. node index.mjs will print file://.../repro/index.mjs
4. npx vite-node index.mjs will print

Need to install the following packages:
[email protected]
Ok to proceed? (y)

/home/gautier/repro/index.mjs:1
'use strict';async (__vite_ssr_import__,__vite_ssr_dynamic_import__,__vite_ssr_exports__,__vite_ssr_exportAll__,__vite_ssr_import_meta__,require,exports,module,__filename,__dirname)=>{{console.log(__vite_ssr_import_meta__.resolve("./index.mjs"));

                                                                                                      ^

TypeError: __vite_ssr_import_meta__.resolve is not a function
    at /home/gautier/repro/index.mjs:1:25
    at ViteNodeRunner.runModule (file:///home/gautier/.npm/_npx/f2342a4b64a2bc92/node_modules/vite-node/dist/client.mjs:399:11)
    at ViteNodeRunner.directRequest (file:///home/gautier/.npm/_npx/f2342a4b64a2bc92/node_modules/vite-node/dist/client.mjs:381:16)
    at ViteNodeRunner.cachedRequest (file:///home/gautier/.npm/_npx/f2342a4b64a2bc92/node_modules/vite-node/dist/client.mjs:206:14)
    at ViteNodeRunner.executeFile (file:///home/gautier/.npm/_npx/f2342a4b64a2bc92/node_modules/vite-node/dist/client.mjs:169:12)
    at CAC.run (file:///home/gautier/.npm/_npx/f2342a4b64a2bc92/node_modules/vite-node/dist/cli.mjs:99:5)

Node.js v20.18.0

System Info

System:
    OS: Linux 5.15 Ubuntu 24.04.1 LTS 24.04.1 LTS (Noble Numbat)
    CPU: (16) x64 AMD Ryzen 7 4800HS with Radeon Graphics
    Memory: 3.52 GB / 7.47 GB
    Container: Yes
    Shell: 5.9 - /home/linuxbrew/.linuxbrew/bin/zsh
  Binaries:
    Node: 20.18.0 - ~/.pkgx/nodejs.org/v20.18.0/bin/node
    npm: 10.9.1 - ~/.pkgx/npmjs.com/v10.9.1/bin/npm
    vite-node: 2.1.5

Used Package Manager

npm

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
• The provided reproduction is a minimal reproducible example of the bug.

[hi-ogawa]

There was some discussions in the past (and my attempt #5188), but unfortunately we cannot implement it properly on vite-node / Vitest currently.

[GauBen]

Thanks @hi-ogawa! By any chance, is Vite 6 bringing the team one step closer to implementing import.meta.resolve?

[sheremet-va]

Thanks @hi-ogawa! By any chance, is Vite 6 bringing the team one step closer to implementing import.meta.resolve?

No, import.meta.resolve is still not available even in Vite Module Runner

[aklinker1]

I was able to work around this, but it's not pretty. In my specific case, it's an E2E test, so I want to have it actually resolve the path to the requested module.

// vitest.config.ts
export default defineConfig({
  test: {
    setupFiles: ["./vitest.setup.ts"],
  },
});

// vitest.setup.ts
import { vi } from 'vitest';
import { createRequire } from 'node:module';

vi.stubGlobal('globalCreateRequire', createRequire);

// source file that uses `import.meta.resolve`...

// ...

// At the very bottom:
if (typeof __vite_ssr_import_meta__ !== 'undefined') {
  __vite_ssr_import_meta__.resolve = (path: string) =>
    'file://' + globalCreateRequire(import.meta.url).resolve(path);
}

We create globalCreateRequire in the setup file so we don't have to add an import for createRequire in the source-code.

You have to put that footer in every source file that uses import.meta.resolve, because it seems like the __vite_ssr_import_meta__ is defined per-file.