oclif / plugin-plugins

plugins plugin for oclif

oclif/plugin-plugins Issues

Use of system dependent path in `install` description results incorrect path in README
Closed 2 months ago
`plugins --json` yields TypeError: Converting circular structure to JSON
Closed 2 months ago9
Would it be possible to use the system's npm?
Closed 3 months ago5
Provide more info about installation failure
Closed 4 months ago1
[BUG] Yarn hoisting behaviour depends on plugin installation order
Closed 4 months ago1
Bug: plugin install can fail due to dependencies releasing incompatible versions
Closed 4 months ago
can't use `NO_PROXY` env var if proxy is configured via `.yarnrc`
Closed 4 months ago1
Is there a way to require a minimum version of the underlying CLI for plugins?
Updated 4 months ago1
Subsequent github url installs fail with `Cannot find module ... yarn/bin/yarn.js`
Closed 9 months ago1
Global .yarnrc yarn path can specify different yarn version breaking plugin-plugins
Closed 9 months ago
[Security] v2.0.1 has dependencies to vulnerable packages
Closed 9 months ago1
💡 Allow customization of the package name prefix for friendly names
Closed 9 months ago
Allow specifying yarn network timeout during install
Closed 9 months ago2
Silent yarn installation to suppress package dep warnings
Closed 9 months ago
package should not use `yarn` as transitive dep
Closed 9 months ago6
display package fullname in plugins list
Closed 9 months ago
Support standard NodeJS versions with NPM
Closed 9 months ago2
Commands as dependencies
Closed 9 months ago5
Programmatically install or detect installed plugins
Closed 9 months ago3
v2.x of this plugin is not compatible with node-14 since @oclif/core@2.9.1
Closed a year ago
Potential command injection vulnerability in plugin-plugins
Closed a year ago1
Why does linking a plugin needs to refresh `node_modules` first?
Closed a year ago
Linking broken after compiling modules that have Typescript dev dependency
Closed a year ago1
Plugins cannot be installed from a private registry that requires login
Closed 2 years ago
Friendly name package resolution fails if npm is not installed
Closed 2 years ago1
Install plugin from private registry
Closed 2 years ago1
Why is yarn a direct dependency?
Closed 5 years ago12
node_modules for already installed plugin resets on installing a new plugin
Closed 4 years ago4
Install location
Closed 4 years ago2
plugins:add fails silently if yarn fails
Closed 4 years ago4
Unable to `require('@oclif/plugin-plugins')` after tslib update
Closed 4 years ago3
update hook fails silently on `yarn add` errors
Closed 4 years ago3
TypeError: Cannot read property 'dim' of undefined
Closed 5 years ago3
Support for channels
Closed 4 years ago1
An in-range update of load-json-file is breaking the build 🚨
Closed 6 years ago1
An in-range update of yarn is breaking the build 🚨
Closed 6 years ago2
An in-range update of @types/node is breaking the build 🚨
Closed 6 years ago7
An in-range update of @oclif/dev-cli is breaking the build 🚨
Closed 6 years ago1
`npm install`does not appear to install anything
Closed 6 years ago1
An in-range update of @oclif/config is breaking the build 🚨
Closed 6 years ago2
An in-range update of @oclif/plugin-help is breaking the build 🚨
Closed 6 years ago1
An in-range update of @oclif/command is breaking the build 🚨
Closed 6 years ago
An in-range update of @oclif/errors is breaking the build 🚨
Closed 6 years ago
An in-range update of cli-ux is breaking the build 🚨
Closed 6 years ago1
An in-range update of debug is breaking the build 🚨
Closed 6 years ago4
Is there a way to highlight that a plugin command being installed will conflict
Closed 6 years ago4
The automated release is failing 🚨
Closed 6 years ago