Replies: 3 comments 4 replies
-
It's certainly possible but I question whether it's actually practical since oclif would need to traverse the entire node_modules to find packages that resemble a plugin. You could cache the result but that first traversal would be (I'm assuming) very slow, especially on windows machines. You might be able to accomplish this using npm's lifecycle scripts. For example, you might be able to use the |
Beta Was this translation helpful? Give feedback.
-
@moltar would defining plugins using wildcards accomplish what you want? I'm thinking oclif could use {
"dependencies": {
"@oclif/core": "^3",
"@oclif/plugin-help": "^6",
"@oclif/plugin-plugins": "^4",
"@org/cool-plugin": "^1",
"@org/awesome-plugin": "^1",
},
"oclif": {
"plugins": [
"@oclif/plugin-*",
"@org/*",
]
}
} |
Beta Was this translation helpful? Give feedback.
-
This is now supported in @oclif/core@3.22.0 |
Beta Was this translation helpful? Give feedback.
-
Would it be possible to do something like this:
And then
@org/cli
would be magically aware of@org/plugin-foo
existence and load it?That is without explicitly specifying the plugin in
oclif.plugins
list.I am also aware of
@oclif/plugin-plugins
, but it's not what I want, but similar. I want to manage plugins exclusively via npm.Beta Was this translation helpful? Give feedback.
All reactions