nx
nx copied to clipboard
fix(core): list local plugins
Current Behavior
Generators from local plugins are not included in the prompt when running nx g without a default collection or specified collection. They are also not present in nx report or nx list
Expected Behavior
Generators from local plugins are present in each expected location. They are separated from installed generators during prompting, s.t. they are more readily available to the user.

Related Issue(s)
Fixes #
☁️ Nx Cloud Report
CI is running/has finished running commands for commit faa2a13d960566f29ce2a3fc5a93a4fcffedc383. 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 12 targets
nx affected --target=e2e --base=b50d3879ab3266d74eccc0dfa60ff8ad82b9b9aa --head=faa2a13d960566f29ce2a3fc5a93a4fcffedc383 --exclude=e2e-storybook,e2e-storybook-angular,e2e-react-native,e2e-detox --parallel=1nx affected --target=test --base=b50d3879ab3266d74eccc0dfa60ff8ad82b9b9aa --head=faa2a13d960566f29ce2a3fc5a93a4fcffedc383 --parallel=1nx affected --target=lint --base=b50d3879ab3266d74eccc0dfa60ff8ad82b9b9aa --head=faa2a13d960566f29ce2a3fc5a93a4fcffedc383 --parallel=3nx affected --target=build --base=b50d3879ab3266d74eccc0dfa60ff8ad82b9b9aa --head=faa2a13d960566f29ce2a3fc5a93a4fcffedc383 --parallel=3nx-cloud record -- yarn nx workspace-lintnx-cloud record -- yarn documentationnx build typedoc-themenx-cloud record -- yarn depchecknx-cloud record -- yarn check-lock-filesnx-cloud record -- yarn check-commitnx-cloud record -- yarn nx format:check --base=b50d3879ab3266d74eccc0dfa60ff8ad82b9b9aa --head=faa2a13d960566f29ce2a3fc5a93a4fcffedc383nx-cloud record -- yarn check-imports
Sent with 💌 from NxCloud.
The latest updates on your projects. Learn more about Vercel for Git ↗︎
| Name | Status | Preview | Updated |
|---|---|---|---|
| nx-dev | ✅ Ready (Inspect) | Visit Preview | Aug 5, 2022 at 10:31PM (UTC) |
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.