fix(vitest): support older NodeJS with async import.meta.resolve

[AriPerkkio]

Description

• fix(vite-node): provide import.meta.filename and dirname #5011 (comment)

import.meta.resolve can be asynchronous in older Node versions like my 18.17.1:

• esm: convert resolve hook to synchronous nodejs/node#43363
• Revert "esm: convert resolve hook to synchronous" nodejs/node#43526

Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

• It's really useful if your PR references an issue where it is discussed ahead of time. If the feature is substantial or introduces breaking changes without a discussion, PR might be closed.
• Ideally, include a test that fails without this PR but passes with it.
• Please, don't make changes to pnpm-lock.yaml unless you introduce a new test example.

Tests

• Run the tests with pnpm test:ci.

Documentation

• If you introduce new functionality, document it. You can run documentation with pnpm run docs command.

Changesets

• Changes in changelog are generated from PR name. Please, make sure that it explains your changes in an understandable manner. Please, prefix changeset messages with feat:, fix:, perf:, docs:, or chore:.

[netlify]

✅ Deploy Preview for fastidious-cascaron-4ded94 canceled.

Name	Link
🔨 Latest commit	ae1d72f
🔍 Latest deploy log	https://app.netlify.com/sites/fastidious-cascaron-4ded94/deploys/65b289f5689a1f0008730396

[hi-ogawa]

Looks good!

If I remember correctly, there is one more relatively recent change with --experimental-import-meta-resolve regarding whether it throws or not when not found:

• import.meta.resolve non existing paths. nodejs/node#49010

NodeJS was throwing an error at some point, but Web spec doesn't throw, so NodeJS aligned with it. Does anyone know if Vitest's vm could be affected by this behavior?

[sheremet-va]

Does anyone know if Vitest's vm could be affected by this behavior?

Oh we need to test this, probably not much has changed in terms of code running because the error will just move to the loader, but this is not how Node works, so it's a potential bug

[hi-ogawa]

Oh we need to test this, probably not much has changed in terms of code running because the error will just move to the loader, but this is not how Node works, so it's a potential bug

Right, I expected it would be an error anyway, but it looks like there is a slight difference after v20.6.0 (which started non-throwing behavior). I added a test case here #5053 and will investigate if there is a way to surface an error similar to node.