-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
feat(react): make vitest the default test runner since it supports ESM and different moduleResolution better #28153
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
☁️ Nx Cloud ReportCI is running/has finished running commands for commit c8b87a7. As they complete they will appear below. Click to see the status, the terminal output, and the build insights. 📂 See all runs for this CI Pipeline Execution ✅ Successfully ran 4 targets
Sent with 💌 from NxCloud. |
f2c07f3
to
3706344
Compare
3706344
to
9f1003f
Compare
9f1003f
to
80ef702
Compare
80ef702
to
7c68633
Compare
7c68633
to
a1fc781
Compare
a1fc781
to
ff3cda0
Compare
ff3cda0
to
3dc21a3
Compare
…M and different moduleResolution better
3dc21a3
to
c8b87a7
Compare
This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request. |
This PR updates the default test runner for React/Web apps to be
vitest
. It aligned better with our emphasis on modern tooling, and the lack of ESM and proper TS support (usingmodule
other thancommonjs
) in Jest makes it hard to use in some workspaces.Current Behavior
Expected Behavior
Related Issue(s)
Fixes #