Unable to import commonjs file with absolute path

[danez]

Describe the bug

When I try to import a commonjs file with an absolute path (e.g. /tmp/something.js) vitest fails to resolve the relative dependencies of this just-imported file.

So for example if I have

// /tmp/function.js
module.exports = require('./function2.js')

// /tmp/function2.js
module.exports  = 2

and in my test I try to do

import('/tmp/function.js')

I get

Error: Cannot find module './fixture2.js'
Require stack:
- /Users/username/Projects/tests/vitest-import-absolute/tmp/fixture.js

Which is also not a real path.

When I try the same thing with ESM and mjs files it works.

Reproduction

https://github.com/danez-labs/vitest-absolute-import/

Clone and run npm test.

There are two tests, one that fails, although it should work, the other uses /@fs/ as a workaround and works, but it is not a real solution.

System Info

System:
    OS: macOS 12.6.1
    CPU: (10) arm64 Apple M1 Pro
    Memory: 329.33 MB / 32.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 18.10.0 - ~/.asdf/installs/nodejs/18.10.0/bin/node
    Yarn: 1.22.19 - /opt/homebrew/bin/yarn
    npm: 8.19.2 - ~/.asdf/plugins/nodejs/shims/npm
  Browsers:
    Safari: 16.1
  npmPackages:
    vite: ^3.2.0 => 3.2.0 
    vitest: ^0.24.3 => 0.24.3

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.

[sheremet-va]

Cannot open reproduction:

The 'danez-labs/vitest-absolute-import' repository doesn't contain the 'tests/main.test.ts' path in 'main'

[danez]

Cannot open reproduction:

Oopps, yes, I renamed the test afterwards. Here is the link to the repo: https://github.com/danez-labs/vitest-absolute-import/

[sheremet-va]

This issue is cause by the same problem as #1864 (root is added before actual absolute path)

[sheremet-va]

Fixed with #1868, released in 0.24.4

[danez]

Thanks for the quick fix. I can confirm this works now.