-
Notifications
You must be signed in to change notification settings - Fork 5
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
[POC]: migrate to vitest #11
base: main
Are you sure you want to change the base?
[POC]: migrate to vitest #11
Conversation
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.
You technically don't even need this file, but maybe it still makes sense to keep it around for reference
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 contemplated not adding it, but I think it's nice just to keep it around. I dont need "environment" either, but I think it's nice to keep it around just to be explicit.
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.
@KonnorRogers Thanks for this PR, but...
- It's surprising (no previous discussion), and it doesn't explain why we want to migrate from jest to vitest (TIL).
- Why did you remove
package-lock.json
in the context of this PR? If that is a change to that you suggest to make, please open a different PR.
Konnor, don't get me wrong, I appreciate you taking care of this, it's just about OSS governance. 🙂
@jodosha Probably should've added a [POC] onto this 😭 and provided context.
https://ruby.social/@timriley/111210945213541284
|
Notes: there is a
--threads="false"
in the runner. This is because of theprocesss.chdir
call.vitest-dev/vitest#566