feat: support plugins with wildcards #978
Merged
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.
Allow plugins to be defined with minimatch patterns. For instance:
This PR also exposes a new option on
Config
calledpluginAdditions
that informsConfig
of additional plugins that should be loaded. This is solves the use case described in #976pluginAdditions
is defined as:Example:
QA
yarn && yarn build
oclif generate my-cli
cd my-cli && yarn link @oclif/core
plugins
entry in package.json to"plugins": ["@oclif/plugin-*"]
bin/dev.js
should shouldhelp
andplugins
topicsbin/dev.js plugins --core
should show plugin-help and plugin-pluginsplugins
from package.jsonbin/run.js
to:bin/dev.js
should shouldhelp
andplugins
topicsbin/dev.js plugins --core
should show plugin-help and plugin-pluginsoclif generate another-cli
cd another-cli && yarn add @oclif/plugin-version
bin/dev.js
ofmy-cli
to:bin/dev.js
should shouldhelp
,plugins
, andversion
topics/commandsbin/dev.js plugins --core
should show plugin-help, plugin-plugins, and plugin-versionCloses #976
Closes oclif/oclif#1235