vitest/test/path-resolution/package.json
Simon Abbott 6c3d708da6
fix: don't use resolved paths if they don't actually exist (#1868)
Previously `toFilePath` would treat _any_ absolute path that doesn't
start with the `root` (usually the current working directory) as a
relative path, which resulted in some seriously mangled paths. Now we
actually check if that resolved path exists before committing to it.

This fixes #1864.
2022-10-31 10:36:54 +01:00

16 lines
362 B
JSON

{
"name": "@vitest/test-path-resolution",
"type": "module",
"private": true,
"scripts": {
"test": "vitest",
"coverage": "vitest run --coverage"
},
"devDependencies": {
"@edge-runtime/vm": "1.1.0-beta.26",
"@vitest/test-path-resolution-target": "workspace:*",
"@vitest/web-worker": "workspace:*",
"vitest": "workspace:*"
}
}