nx
nx copied to clipboard
fix(core): do not build the project graph in nx report if there's no native support
Current Behavior
If we're on a system that does not have native support, nx report will still try to build the project graph.
Because some dependencies for the project graph uses native code, nx report will output incorrect messages
Expected Behavior
Nx report does not try to use the project graph when generating the report when there's no native support
Related Issue(s)
Fixes #
The latest updates on your projects. Learn more about Vercel for Git ↗︎
| Name | Status | Preview | Comments | Updated (UTC) |
|---|---|---|---|---|
| nx-dev | ✅ Ready (Inspect) | Visit Preview | 💬 Add feedback | Jun 16, 2023 6:24pm |
☁️ Nx Cloud Report
CI is running/has finished running commands for commit 7cc80952a1ef084ad64d41c83118329efede6193. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.
📂 See all runs for this branch
✅ Successfully ran 8 targets
nx affected -t e2e-macos --parallel=1 --base=e2217a9350a5d3b403c33b4aae5384fb7960bf32 --head=7cc80952a1ef084ad64d41c83118329efede6193nx affected --target=e2e --base=e2217a9350a5d3b403c33b4aae5384fb7960bf32 --head=7cc80952a1ef084ad64d41c83118329efede6193 --parallel=1nx affected --target=test --base=e2217a9350a5d3b403c33b4aae5384fb7960bf32 --head=7cc80952a1ef084ad64d41c83118329efede6193 --parallel=1nx affected --target=build --base=e2217a9350a5d3b403c33b4aae5384fb7960bf32 --head=7cc80952a1ef084ad64d41c83118329efede6193 --parallel=3nx run-many -t check-imports check-commit check-lock-files depcheck check-codeowners documentation --parallel=1 --no-dtenx affected --target=lint --base=e2217a9350a5d3b403c33b4aae5384fb7960bf32 --head=7cc80952a1ef084ad64d41c83118329efede6193 --parallel=3nx-cloud record -- nx format:check --base=e2217a9350a5d3b403c33b4aae5384fb7960bf32 --head=7cc80952a1ef084ad64d41c83118329efede6193nx documentation --no-dte
Sent with 💌 from NxCloud.
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.