Vitest not starting up due to failed version check on windows #88

daple · 2022-09-29T09:54:46Z

Describe the bug
Hi there,
Every time I start up vscode it keeps telling me,
"Because Vitest version < 0.12.0 for every workspace folder, run/debug/watch tests from Vitest extension disabled."

Tried uninstall / install but it won't come up again.

Sth. I should be aware off ?

Thx!

To Reproduce
have vitest 0.23.4 installed, used the cmd: npm init vue@3 to create a totally new package

installed your vitest extension.

Restart vscode, see error appearing.

Expected behavior
possible to start the tests through test explorer or using the green play icon

Screenshots
If applicable, add screenshots to help explain your problem.

Environment
windows 10, vscode :
Version: 1.71.2 (user setup)
Commit: 74b1f979648cc44d385a2286793c226e611f59e7
Datum: 2022-09-14T21:03:37.738Z
Electron: 19.0.12
Chromium: 102.0.5005.167
Node.js: 16.14.2
V8: 10.2.154.15-electron.0
Betriebssystem: Windows_NT x64 10.0.19044
Sandkasten: No

OS: [e.g. macOS]
VSCode version:
Vitest version:
Vitest plugin version:

Additional context
same setup on macos works

gaokun · 2022-09-30T03:15:25Z

I got the same warning on MacOS

Vitest Plugin: 0.2.29
Vitest: 0.23.4
vscode: 1.17.2
MacOS: 11.4

Ewocker · 2022-10-08T00:11:11Z

same warning on MacOS

philwolstenholme · 2022-10-08T20:58:41Z

I have the same issue on a Mac, here's an example repo https://github.com/philwolstenholme/wolstenhol-11ty/

Extension version v0.2.29
Vitest version 0.24.0
Vite version: 3.1.0

dalilakatialeo · 2022-10-14T00:14:57Z

Same issue on Ubuntu 20.04.5.

Extension version v0.2.32
Vitest version 0.22.1
Vite version: 3.0.8
vscode: 1.72.0

JAKimball · 2022-11-05T05:00:16Z

I've seen this as well on Windows with Ubuntu 22.04 on WSL. I suspect the root cause could be a bug in vscode-server.

At least in my case when I've seen this, shutting down all VSCode instances and restarting has cleared up the problem, but it still re-occurs at random. I'll try to investigate a bit more if I see it again.

I suspect when this happens the extension does not even have a Vitest version number.

odranoelBR · 2022-11-07T14:05:11Z

Same issue on Ubuntu 22.04
Extension version v0.2.32
Vitest version 0.24.3
Vite version: 3.1.4
vscode: 1.73.0

toniengelhardt · 2022-11-17T13:36:57Z

Same, doesn't run tests on OS X Ventura.

darioielardi · 2022-11-19T16:25:53Z

Same here:
macOS 13.0.1
Vitest 0.25.2
vitest-vscode 0.2.34

Lauro235 · 2023-01-03T14:37:33Z

Same here
Windows 11
Vitest 0.26.3
vitest-vscode 0.2.35

I clicked Vitest: Enable assuming that was required...

…est-dev#88

ngirardin · 2023-01-10T17:04:02Z

I think that I found a fix: the problem seems to come from node not being installed globally, but by a version manager (in my case n).

Lauro235 · 2023-01-10T18:06:56Z

I think that I found a fix: the problem seems to come from node not being installed globally, but by a version manager (in my case n).

This makes perfect sense, I have nvm for windows, I wonder how many people share the same environment...

Just out of curiosity, what are the next steps in a case like this? Do people take it on themselves to try to fix the bug? Have you already done that? Apologies if that's a noob question!

bradenbiz · 2023-01-13T16:40:07Z

I think that I found a fix: the problem seems to come from node not being installed globally, but by a version manager (in my case n).

I can confirm this. I originally installed Node on my MacOS machine via NVM, and I was having this issue. I just went and downloaded the installer from https://nodejs.org/en/download/ and installed Node through the wizard.

Restarted VSCode a couple times, and now I'm getting test results in the UI!

ngirardin · 2023-01-13T17:27:02Z

Thanks for the reproduction. The issue is not limited to Windows, I'm having it on macOS as well.

As for the next step, I've created a PR (#118), I'm waiting for the maintainers to review it.

lucaspereirasouzat · 2023-01-17T21:04:32Z

same problem here

JAKimball · 2023-01-20T08:41:15Z

Sorry, but the "fix" in PR #118 actually caused this to start happening again for me. I had to revert to the previous version (v0.2.36) in order to not get the above error.

Some details:

I'm on Windows with Ubuntu 22.04 on WSL.
All installations of Node are managed via nvm.

At some point in the past, I had set the setting remote.WSL.useShellEnvironment to false. ("If set [true], the WSL windows gets the environment from the shell it was opened from.")

For versions of the extension prior to the current (< v0.2.37), when I set remote.WSL.useShellEnvironment back to the default (true), the extension would identify the vitest version correctly, provided that VSCode was started from the Linux command line in the proper environment (as opposed to the Windows desktop where it would still fail).

For the current version (v0.2.37), I get Vitest version = undefined and Because Vitest version < 0.12.0 ... regardless of the remote.WSL.useShellEnvironment setting. Reverting to the previous extension version now fixes the problem for me.

ngirardin · 2023-01-21T14:12:05Z

Hi Jonathan, (I'm not the maintainer, just a contributor) I'm sorry that the change broke your setup. I don't have any windows machine to reproduce the bug. I don't know if there's a reliable way to determine when we should pass the process.execPath param or not (maybe there are some env variables that differ?). We could maybe do it this way: - launch vitest without passing the process.execPath - if it fails, launch it with the process.execPath param. Lorentz, Braden, Lucas the fix was merged, does it now work on your end? Best, Nicolas

…

On Fri, Jan 20, 2023 at 9:41 AM Jonathan Kimball ***@***.***> wrote: Sorry, but the "fix" in PR #118 <#118> actually caused this to start happening again for me. I had to revert to the previous version (v0.2.36) in order to not get the above error. Some details: - I'm on Windows with Ubuntu 22.04 on WSL. - All installations of Node are managed via nvm. At some point in the past, I had set the setting remote.WSL.useShellEnvironment to *false*. ("If set [true], the WSL windows gets the environment from the shell it was opened from.") For versions of the extension prior to the current (< v0.2.37), when I set remote.WSL.useShellEnvironment back to the default (*true*), the extension would identify the vitest version correctly, provided that VSCode was started from the Linux command line in the proper environment (as opposed to the Windows desktop where it would still fail). For the current version (v0.2.37), I get Vitest version = undefined and Because Vitest version < 0.12.0 ... regardless of the remote.WSL.useShellEnvironment setting. Reverting to the previous extension version now fixes the problem for me. — Reply to this email directly, view it on GitHub <#88 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAENRQHQVUTCKKICGZGD3VLWTJFTNANCNFSM6AAAAAAQYTBHZY> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

aniketicloud · 2023-01-22T08:19:49Z

I am getting the same error on Windows.

ngirardin · 2023-01-22T08:47:16Z

Hi Aniket, I'll try to work on a fix.

…

On Sun, Jan 22, 2023 at 9:20 AM Aniket Pandharabale < ***@***.***> wrote: I am getting the same error on Windows. — Reply to this email directly, view it on GitHub <#88 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAENRQEOQLJS56TORIPFMZLWTTUTBANCNFSM6AAAAAAQYTBHZY> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

ngirardin · 2023-01-22T15:22:56Z

@JAKimball @aniketicloud, could you try #125 to see if it fixes the issue?

- git clone https://github.com/ngirardin/vscode.git
- git checkout better-version-detection  
- npm install
- npm run compile
- Click on "Run and Debug", then in the panel select "Run Extension Base" and click on the play icon

A new VSCode window will open, try to open a few projects, and please let me know if the extensions detect the version.

asbermudez · 2023-01-23T10:03:29Z

@ngirardin Works with the project I was having issues :)

aniketicloud · 2023-01-23T18:11:23Z

@JAKimball @aniketicloud, could you try #125 to see if it fixes the issue?
- git clone https://github.com/ngirardin/vscode.git
- git checkout better-version-detection  
- npm install
- npm run compile
- Click on "Run and Debug", then in the panel select "Run Extension Base" and click on the play icon
A new VSCode window will open, try to open a few projects, and please let me know if the extensions detect the version.

I followed the same steps.
In vscode root folder, the Vitest plugin is not able to get the version.
When I did Run and Debug, then new VS Code opened. In this new window, I clicked on run the test (left side arrow in test file), but now test runs and are not stopping.

ngirardin · 2023-01-25T06:45:05Z

@mrcaidev did you tried the steps in #88 (comment) ?

mrcaidev · 2023-01-26T03:30:37Z

@mrcaidev did you tried the steps in #88 (comment) ?

npm run compile can't resolve birpc and flatted.

Error log

CLI Building entry: ./src/extension.ts
CLI Using tsconfig: tsconfig.json
CLI tsup v5.12.9
CLI Target: node12
CJS Build start
✘ [ERROR] Could not resolve "birpc"

    src/pure/watch/ws-client.ts:5:28:
      5 │ import { createBirpc } from 'birpc'
        ╵                             ~~~~~~~

  You can mark the path "birpc" as external to exclude it from the bundle, which will remove this
  error.

✘ [ERROR] Could not resolve "flatted"

    src/pure/watch/ws-client.ts:6:33:
      6 │ import { parse, stringify } from 'flatted'
        ╵                                  ~~~~~~~~~

  You can mark the path "flatted" as external to exclude it from the bundle, which will remove this
  error.

CJS Build failed
Error: Build failed with 2 errors:
src/pure/watch/ws-client.ts:5:28: ERROR: Could not resolve "birpc"
src/pure/watch/ws-client.ts:6:33: ERROR: Could not resolve "flatted"

...

ngirardin · 2023-01-26T08:26:31Z

Did you run `npm install` first?

…

On Thu, Jan 26, 2023 at 4:30 AM Yuwang Cai ***@***.***> wrote: @mrcaidev <https://github.com/mrcaidev> did you tried the steps in #88 (comment) <#88 (comment)> ? npm run compile can't resolve birpc and flatted. Error log CLI Building entry: ./src/extension.ts CLI Using tsconfig: tsconfig.json CLI tsup v5.12.9 CLI Target: node12 CJS Build start ✘ [ERROR] Could not resolve "birpc" src/pure/watch/ws-client.ts:5:28: 5 │ import { createBirpc } from 'birpc' ╵ ~~~~~~~ You can mark the path "birpc" as external to exclude it from the bundle, which will remove this error. ✘ [ERROR] Could not resolve "flatted" src/pure/watch/ws-client.ts:6:33: 6 │ import { parse, stringify } from 'flatted' ╵ ~~~~~~~~~ You can mark the path "flatted" as external to exclude it from the bundle, which will remove this error. CJS Build failed Error: Build failed with 2 errors: src/pure/watch/ws-client.ts:5:28: ERROR: Could not resolve "birpc" src/pure/watch/ws-client.ts:6:33: ERROR: Could not resolve "flatted" ... — Reply to this email directly, view it on GitHub <#88 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAENRQC4VAJMZIEJUQMAHFDWUHVWRANCNFSM6AAAAAAQYTBHZY> . You are receiving this because you were mentioned.Message ID: ***@***.***>

mrcaidev · 2023-01-26T08:34:21Z

Did you run npm install first?

Solved. I installed it with pnpm and somehow the dependencies broke, but with npm it works well.

And the extension works perfectly in the debug session. ❤️

ngirardin · 2023-01-26T09:52:07Z

Thanks, I'm glad to be here! I'm waiting for a maintainer to merge the pull request.

…

On Thu, Jan 26, 2023 at 9:34 AM Yuwang Cai ***@***.***> wrote: Did you run npm install first? … <#m_3573095887877003356_> On Thu, Jan 26, 2023 at 4:30 AM Yuwang Cai *@*.*> wrote: @mrcaidev <https://github.com/mrcaidev> https://github.com/mrcaidev <https://github.com/mrcaidev> did you tried the steps in #88 <#88> (comment) <#88 (comment) <#88 (comment)>> ? npm run compile can't resolve birpc and flatted. Error log CLI Building entry: ./src/extension.ts CLI Using tsconfig: tsconfig.json CLI tsup v5.12.9 CLI Target: node12 CJS Build start ✘ [ERROR] Could not resolve "birpc" src/pure/watch/ws-client.ts:5:28: 5 │ import { createBirpc } from 'birpc' ╵ ~~~~~~~ You can mark the path "birpc" as external to exclude it from the bundle, which will remove this error. ✘ [ERROR] Could not resolve "flatted" src/pure/watch/ws-client.ts:6:33: 6 │ import { parse, stringify } from 'flatted' ╵ ~~~~~~~~~ You can mark the path "flatted" as external to exclude it from the bundle, which will remove this error. CJS Build failed Error: Build failed with 2 errors: src/pure/watch/ws-client.ts:5:28: ERROR: Could not resolve "birpc" src/pure/watch/ws-client.ts:6:33: ERROR: Could not resolve "flatted" ... — Reply to this email directly, view it on GitHub <#88 (comment) <#88 (comment)>>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAENRQC4VAJMZIEJUQMAHFDWUHVWRANCNFSM6AAAAAAQYTBHZY <https://github.com/notifications/unsubscribe-auth/AAENRQC4VAJMZIEJUQMAHFDWUHVWRANCNFSM6AAAAAAQYTBHZY> . You are receiving this because you were mentioned.Message ID: @.*> Solved. I installed it with pnpm and somehow the dependencies broke, but with npm it works well. And the extension works perfectly in the debug session. ❤️ — Reply to this email directly, view it on GitHub <#88 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAENRQBBQGZ6CWMVQXPZ4HDWUIZJTANCNFSM6AAAAAAQYTBHZY> . You are receiving this because you were mentioned.Message ID: ***@***.***>

mikestopcontinues · 2023-01-30T15:03:15Z

Not every workspace root in my project is a JS project. But I think I should still be able to use run/debug/watch in my JS workspace roots. Will #125 work for my case? I ask because the error message suggests it may not...

braebo · 2023-02-04T19:50:25Z

Is there a workaround for pnpm users while we wait for #125?

zxch3n · 2023-02-08T13:40:41Z

@ngirardin 's PR is merged and released now. Is it still happening? @JAKimball

ffxsam · 2023-02-08T16:45:10Z

Works great now, thanks!

ngirardin · 2023-02-09T08:34:10Z

Thank you everyone for the feedback 🤗

pearone · 2023-02-21T03:03:54Z

pnpm +1

mrcaidev · 2023-03-26T03:19:21Z

Still an issue.

Version: v0.2.39
Environment: WSL2, pnpm monorepo
Log:

[INFO 11:11:56 AM] Vitest Workspace [MY PROJECT NAME]: Vitest version = undefined
[Error 11:11:56 AM] Because Vitest version < 0.12.0 for every workspace folder, run/debug/watch tests from Vitest extension disabled.

liana-p · 2023-04-10T12:43:36Z

I'm also having this issue. using nvm for windows and pnpm

kwiniarski · 2023-04-21T16:58:04Z

Lately I had the same issue with latest extension and Vitest (Windows, fnm & pnpm). As my repository is a monorepo, I had Vitest installed in specific packages. The solution was to hoist Vitest to the root node_modules folder. You can do that with pnpm by adding public-hoist-pattern[]=*vitest* to your .npmrc file in the project root folder.

mrcaidev · 2023-04-22T02:49:36Z

Solved with Vitest Workspace:

import { defineWorkspace } from "vitest/config";

export default defineWorkspace(["packages/*", "apps/*"]);

And nothing else.

Plus, I installed Vitest in the monorepo root.

imanwarsame · 2023-04-27T18:34:24Z

Not working for me, I am not using a monorepo. Using windows. Error text reads as follows
Because Vitest version < 0.12.0 for every workspace folder, run/debug/watch tests from Vitest extension disabled.

wighawag · 2023-05-07T13:17:13Z

I have having the same issue, no monorepo but pnpm

Khanh2050 · 2023-06-06T11:18:32Z

Seem like newest version bring back this issue - or at least on my Windows.
When I downgrade back to 0.2.39 , the issue is gone and Vitest starti working normal again

Vikms95 · 2023-06-13T21:22:54Z

Seem like newest version bring back this issue - or at least on my Windows. When I downgrade back to 0.2.39 , the issue is gone and Vitest starti working normal again

Having this same issue, tried the steps above and I was not able to figure it out. I'll downgrade for now.

deka · 2023-06-23T14:08:37Z

related with #116 ?

OrvilleTheDuck · 2023-09-19T15:58:08Z

I fixed this issue on Windows by moving my code from a path with spaces to one without.

When the extension calls vitest.cmd to get the version if the path has spaces in it the command fails.

Trying to get vitest version from c:\<Path To Code With Spaces>\node_modules\.bin\vitest.cmd -v...

Extension Version: 0.2.42
Vitest Version: 0.33.0
OS: Windows

borgmon · 2023-12-14T23:27:35Z

I am using n, pnpm, monorepo.
I solved it by adding vitest to the root package.json and reloading the vscode window, in addition to this change

Solved with Vitest Workspace:
import { defineWorkspace } from "vitest/config";

export default defineWorkspace(["packages/*", "apps/*"]);
And nothing else.

Plus, I installed Vitest in the monorepo root.

aurelienbobenrieth · 2023-12-15T10:41:06Z

@keith-harrison-iopt Thank you my dear sir!
I had the exact same issues, removed existing spaces from my dir path fixed it as well !

firatoezcan · 2024-01-19T12:36:50Z

If anyone stumbled upon this, I've debugged it for a really long time and at the end the issue was that the vitest command couldn't be ran because my project was using a postcss.config.js with type: "module".

If it somehow doesn't work in your workspace, try running this command to see if the server is even able to spin up properly:

./node_modules/.bin/vitest --api.port 39154 --api.host 127.0.0.1

If this fails, resolve those issues and reload the window when it runs without crashing

daple added the p3-minor-bug An edge case that only affects very specific usage (priority) label Sep 29, 2022

ngirardin mentioned this issue Jan 10, 2023

Vitest not starting up due to failed version check on ubuntu #102

Closed

ngirardin added a commit to ngirardin/vscode that referenced this issue Jan 10, 2023

Fix Vitest not starting up due to failed version check on windows vit…

f981f1c

…est-dev#88

ngirardin mentioned this issue Jan 10, 2023

Fix Vitest not starting up due to failed version check on windows #88 #118

Merged

JAKimball mentioned this issue Jan 21, 2023

Vitest version not detected #124

Closed

This was referenced Jan 22, 2023

Vitest plugin executes non test files #90

Closed

fix: Add better version detection #125

Merged

Use closest vitest.config.ts from the test file for mono repo #13

Closed

Tests not runnable on Linux #31

Closed

IgorKrupenja mentioned this issue Feb 2, 2023

VSCode Vitest extension is broken IgorKrupenja/nextjs-monorepo-starter#14

Open

2 tasks

zxch3n closed this as completed Feb 9, 2023

doei mentioned this issue Mar 21, 2023

Vitest version = undefined #142

Closed

DetachHead mentioned this issue Jul 10, 2023

Vitest not starting up due to failed version check on windows #170

Closed

mzietlow mentioned this issue Dec 8, 2023

Vitest version not detected when workspace path has spaces in it #200

Closed

github-actions bot locked and limited conversation to collaborators Feb 27, 2024

Vitest not starting up due to failed version check on windows #88

Vitest not starting up due to failed version check on windows #88

Comments

daple commented Sep 29, 2022

gaokun commented Sep 30, 2022

Ewocker commented Oct 8, 2022

philwolstenholme commented Oct 8, 2022 • edited Loading

dalilakatialeo commented Oct 14, 2022

JAKimball commented Nov 5, 2022

odranoelBR commented Nov 7, 2022

toniengelhardt commented Nov 17, 2022

darioielardi commented Nov 19, 2022

Lauro235 commented Jan 3, 2023

ngirardin commented Jan 10, 2023

Lauro235 commented Jan 10, 2023

bradenbiz commented Jan 13, 2023 • edited Loading

ngirardin commented Jan 13, 2023 • edited Loading

lucaspereirasouzat commented Jan 17, 2023

JAKimball commented Jan 20, 2023

ngirardin commented Jan 21, 2023 via email

aniketicloud commented Jan 22, 2023

ngirardin commented Jan 22, 2023 via email

ngirardin commented Jan 22, 2023 • edited Loading

asbermudez commented Jan 23, 2023

aniketicloud commented Jan 23, 2023

ngirardin commented Jan 25, 2023

mrcaidev commented Jan 26, 2023

ngirardin commented Jan 26, 2023 via email

mrcaidev commented Jan 26, 2023 • edited Loading

ngirardin commented Jan 26, 2023 via email

mikestopcontinues commented Jan 30, 2023

braebo commented Feb 4, 2023

zxch3n commented Feb 8, 2023

ffxsam commented Feb 8, 2023

ngirardin commented Feb 9, 2023

pearone commented Feb 21, 2023 • edited Loading

mrcaidev commented Mar 26, 2023

liana-p commented Apr 10, 2023

kwiniarski commented Apr 21, 2023

mrcaidev commented Apr 22, 2023

imanwarsame commented Apr 27, 2023

wighawag commented May 7, 2023

Khanh2050 commented Jun 6, 2023

Vikms95 commented Jun 13, 2023

deka commented Jun 23, 2023

OrvilleTheDuck commented Sep 19, 2023

borgmon commented Dec 14, 2023

aurelienbobenrieth commented Dec 15, 2023

firatoezcan commented Jan 19, 2024

philwolstenholme commented Oct 8, 2022 •

edited

Loading

bradenbiz commented Jan 13, 2023 •

edited

Loading

ngirardin commented Jan 13, 2023 •

edited

Loading

ngirardin commented Jan 22, 2023 •

edited

Loading

mrcaidev commented Jan 26, 2023 •

edited

Loading

pearone commented Feb 21, 2023 •

edited

Loading