feat(core): add --json flag for better AX to nx list#34551
Conversation
✅ Deploy Preview for nx-dev ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for nx-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
View your CI Pipeline Execution ↗ for commit 0a5b13e
☁️ Nx Cloud last updated this comment at |
![nx-cloud[bot]](https://avatars.githubusercontent.com/in/80458?s=60&v=4){kind=small}
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
MaxKless
force-pushed
the
nx-list-json-output
branch
from
e69f625 to
ba9fb5a
Compare
MaxKless
force-pushed
the
nx-list-json-output
branch
from
ba9fb5a to
be4da02
Compare
e2e/nx/src/misc.test.ts
Outdated
| expect(typeof parsed.generators).toBe('object'); | ||
| expect(typeof parsed.executors).toBe('object'); |
There was a problem hiding this comment.
Can we check actual values to some extent here
There was a problem hiding this comment.
Important
At least one additional CI pipeline execution has run since the conclusion below was written and it may no longer be applicable.
Nx Cloud has identified a possible root cause for your failed CI:
We classified this failure as environment_state rather than a code issue. The PR modifies only the nx list command's JSON output functionality, while the failing test is in the unrelated e2e-gradle project testing Gradle daemon integration. The "Gradle build daemon has been stopped" error indicates an external environment state issue with no code path connecting it to our JSON formatting changes.
No code changes were suggested for this issue.
🔂 A CI rerun has been triggered by adding an empty commit to this branch.
🎓 Learn more about Self-Healing CI on nx.dev
### Current Behavior nx list <plugin> shows generator/executor names and descriptions in text format only. It does not show where the plugin or its generators/executors are located on disk, and there is no machine-readable output option. ### Expected Behavior - nx list --json outputs all local and installed plugins with their paths and capability types - nx list <plugin> --json outputs detailed structured JSON including resolved paths to each generator/executor implementation and schema - nx list <plugin> (text mode) now also shows the plugin's root path (cherry picked from commit 1081c32)
### Current Behavior nx list <plugin> shows generator/executor names and descriptions in text format only. It does not show where the plugin or its generators/executors are located on disk, and there is no machine-readable output option. ### Expected Behavior - nx list --json outputs all local and installed plugins with their paths and capability types - nx list <plugin> --json outputs detailed structured JSON including resolved paths to each generator/executor implementation and schema - nx list <plugin> (text mode) now also shows the plugin's root path (cherry picked from commit 1081c32)
|
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. |
2 participants
Current Behavior
nx list shows generator/executor names and descriptions in text format only. It does not show where the plugin or its generators/executors are located on disk, and there is no machine-readable output option.
Expected Behavior