Most fields in Module are missing. （environment: 'node'）

[mokeyish]

Describe the bug

Reproduction

https://stackblitz.com/edit/vitest-dev-vitest-cqnkvq?file=test%2Fbasic.test.ts

System Info

System:
    OS: Linux 5.0 undefined
    CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 0 Bytes / 0 Bytes
    Shell: 1.0 - /bin/jsh
  Binaries:
    Node: 16.14.2 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 7.17.0 - /usr/local/bin/npm
  npmPackages:
    @vitest/ui: latest => 0.31.1 
    vite: latest => 4.3.8 
    vitest: latest => 0.31.1

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.

[stackblitz]

Start a new pull request in StackBlitz Codeflow.

• vitest-dev-vitest-cqnkvq (Open reproduction)

[sheremet-va]

Vitest doesn't currently support an "actual" Node environment, only those features usually needed for cross-environment code because it uses vite-node under the hood which has its own module system. For reference: #2854

[mokeyish]

@sheremet-va Thanks! is there an alternative to get module.path? I use the path to get test files in the relative folder.

[sheremet-va]

@sheremet-va Thanks! is there an alternative to get module.path? I use the path to get test files in the relative folder.

You can get the current module path with import.meta.url

[mokeyish]

You can get the current module path with import.meta.url

Thanks

[sheremet-va]

Strict ESM enhancements are discussed in #2841, closing this issue for now.