Roman
Are you thinking of caching the results with serialized key? I'll be honest, the argument is definitely making it look ugly. But if that's the only way :)
There's also a concept of Shell Plugins: https://developer.1password.com/docs/cli/shell-plugins/
Agreed! Great extension idea, but locks the user into using `npm`. We use `pnpm` on all projects, and thus this cannot work.
`allowedVersions` with scopes does not seem to work. ```json "pnpm": { "peerDependencyRules": { "allowedVersions": { "@ws/my-ws-pkg>aws-cdk-lib": ">=2.100.0" } } }, ``` ``` packages/my-ws-pkg ├─┬ @aws-cdk/app-staging-synthesizer-alpha 2.123.0-alpha.0 │ └── ✕ unmet...
There's also an issue running inside GitHub Workflow. It seems like `pnpm` is not recognizing that the Node version already exists and updated. We have `actions/setup-node@v3` configured to set the...
1. I think the package shall use [undici](https://github.com/nodejs/undici) as this will be the default client in the future Node versions 2. If anything needs to be exposed, then I think...
A few reasons why auto-discovery is a problem: - No support for large projects that may have several unrelated internal CLIs, all in a single repo and `package.json`. - Not...
Does it still need the package.json file with the bundle approach?
I can confirm that @etoulas's solution works for PostgreSQL. Can this be added to the package?
What particularly is lacking currently?