feat(core): expand meaning of plugins array to allow installing non-runtime plugins and inter-opt with installations property #22108
+566
−60
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Current Behavior
Folks using the nx wrapper (nxw.js in .nx) install plugins in nx.json[installation][plugins].
This is a bit weird since there is also nx.json[plugins]
Expected Behavior
You can specify plugins in the top level plugins array.
This PR also adds a field called "runtime" that can be set to false to tell Nx that a plugin worker doesn't need to be spawned for a listed plugin.
This PR fixes up:
nx migrate
support for plugins array contained versionsnx add
, to add plugins to the plugins array by defaultRelated Issue(s)
Fixes #