-
Notifications
You must be signed in to change notification settings - Fork 64
chore: upgrade to vitest 1.0 #141
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.
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
base: master
Are you sure you want to change the base?
Conversation
This is what I am seeing:
The |
@@ -11,7 +11,7 @@ jobs: | |||
|
|||
strategy: | |||
matrix: | |||
node-version: [16.x, 18.x, 20.x] | |||
node-version: [18.x, 20.x, 22.x] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Vitest 1.0 depends on Vite 5, which does not run on Node 16
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am not sure if dropping support (essentially) for Node v16 is a good idea. The current version of Vitest works and there's really no need to upgrade.
I'm not sure why it thinks coverage dropped so much. I'd be surprised if we were really at 100% before. I trust it more with this PR