We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
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
Describe the bug The read path is incorrect when using the resolve function in the two modes of debugging test and running test
To Reproduce Steps to reproduce the behavior on the example project:
Run the test code in debug mode and observe the path value at the debugger
Run the test code directly in regular mode
Expected behavior path value match
Screenshots debugger..... regular mode....
Environment
(Paste info.txt content generated by the example project)
Additional context There is no problem running in webstorm, it should not be a problem with vitest itself
test('foo', () => { const foo = `${resolve()}` debugger expect(foo ).toBe('D:\\project-github\\unplugin-vue-cssvars') })
The text was updated successfully, but these errors were encountered:
Can you please retest with the latest pre-release version of the extension?
Sorry, something went wrong.
No branches or pull requests
Describe the bug
The read path is incorrect when using the resolve function in the two modes of debugging test and running test
To Reproduce
Steps to reproduce the behavior on the example project:
Run the test code in debug mode and observe the path value at the debugger
Run the test code directly in regular mode
Expected behavior
path value match
Screenshots
debugger.....
regular mode....
Environment
(Paste info.txt content generated by the example project)
Additional context
There is no problem running in webstorm, it should not be a problem with vitest itself
The text was updated successfully, but these errors were encountered: