-
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(testing): add disableJestRuntime option to @nx/jest/plugin to speed up target inference #28522
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
☁️ Nx Cloud ReportCI is running/has finished running commands for commit 5b0d672. 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. |
ddf7045
to
9dc11b7
Compare
c8a0c69
to
4e3a629
Compare
4e3a629
to
db2fa15
Compare
db2fa15
to
844cc15
Compare
844cc15
to
6c5f52a
Compare
6c5f52a
to
205babe
Compare
08be074
to
7ba6f2d
Compare
7ba6f2d
to
3974055
Compare
3974055
to
cd9ff8b
Compare
…eed up target inference
cd9ff8b
to
5b0d672
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 adds a new
disableJestRuntime
option to@nx/jest/plugin
. By setting this totrue
, the inference plugin will not usejest-config
andjest-runtime
to retrieveoutputs
, nor matching spec files whenciTargetName
is used. Instead, we'll use our own config loader and glob/matcher to get both values for the inferred targets.This speeds up computation quite a bit. With a large monorepo (800 projects, 75K files), the computation goes from 2m 41s to 35s, or ~78% time reduction.
NOTE: This has no effect on existing projects and needs to be opted into.
Current Behavior
Expected Behavior
Related Issue(s)
Fixes #