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(core): ability to run local nx plugins #9029
Conversation
Nx Cloud ReportCI is running for commit fdf3de5. 📂 Click to track the progress, see the status, the terminal output, and the build insights. Sent with 💌 from NxCloud. |
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/nrwl/nx-dev/GDhxAA47weuUmARykYBhJ3AtoSW7 [Deployment for fdf3de5 canceled] |
b9fc67f
to
6a05080
Compare
6a05080
to
227d5b2
Compare
227d5b2
to
7641644
Compare
CC @vsavkin @FrozenPandaz whenever either of you are ready to review ping me, I'd like to talk through some of the changes on this one. |
a7eb255
to
2c4afe7
Compare
2c4afe7
to
df0c97f
Compare
df0c97f
to
fdf3de5
Compare
fdf3de5
to
7641644
Compare
Superceded by #9116 |
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. |
Current Behavior
Nx plugins are loaded through a combination of
require.resolve
andrequire
. In order for this to work for plugins that were created and live as a project in the workspace, that project must be built and available via NODE_PATH (sometime's done by symlinking outputs to node_modules).This complicates the setup for workspace executors, as dev's must setup some kind of automated build before the command. This can be done either using targetDependencies or a clever post install script, but neither are really ideal.
Expected Behavior
Created nx plugins' functionality is available to the CLI, in the same manner that an installed plugin would be.
Related Issue(s)
Fixes #8824
Fixes #3231