Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

fix: importActual path resolution for non-child paths (fix #1864) #1868

Merged
merged 1 commit into from
Oct 31, 2022
Merged

fix: importActual path resolution for non-child paths (fix #1864) #1868

merged 1 commit into from
Oct 31, 2022

Commits on Oct 28, 2022

  1. fix: don't use resolved paths if they don't actually exist 

    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 vitest-dev#1864.
    @simon-abbott
    simon-abbott committed Oct 28, 2022
    Configuration menu
    Copy the full SHA
    b18f707 View commit details
    Browse the repository at this point in the history