Seems to be broken if you use with other CLI tools while using PNPM as package manager

[RIP21]

Seems to be broken if you use with other CLI tools while using PNPM as package manager

[wtrocki]

Never used CLI with this package manager.
There will be couple places where CLI (and depending packages) will fail. We do not test with anything else than npm or yarn

[RIP21]

You shall start testing with it as it is pretty popular :P
PNPM is major for all people that are using rush.js monorepo management tool. To name a few Microsoft, Revolut and many more.
PNPM is just amazing and IMO how npm should've been working from the day 1 :)

Anyway, mostly 99% of packages are working as is with PNPM, only CLIs are getting broken usually due to bin behavior (which is makes sense as it doesn't leak CLIs (bins) from transitive dependencies)

[tvvignesh]

Just tried installing graphql-cli using PNPM (since that's what I use) and I got the same error:

[RIP21]

Overall GraphQL CLI + Codegen + Inspector add-ons are seem to be very fragile. I cannot specify, but on multiple occasions using those tools through the CLI wrapper, I end up getting issues, so currently I'm using those tools CLIs directly as, fortunately they're working as expected.
And it's with regular npm. I'm not mentioning PNPM that is special.

I would rather keep init and few other commands unique to CLI in it, but rest would've removed for good to simplify maintenance.

As because I think you folks at Guild are having so much products to maintain I see their quality is worsened overtime and is not as perfect as it used to be and in integration they're not working quite often which is annoying.