fix(core): listing plugin capabilities causes issues when returning null #15308
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
loadNxPlugin
may error when trying to load a module which is not an Nx plugin. This is because we set thename
property on the object, which could be readonly, or similar.getPluginCapabilities
returns null on error, and callsloadNxPlugin
.Expected Behavior
getPluginCapabilities
doesn't return null on errorRelated Issue(s)
Fixes #15305