Bad sublibrary gets seen as "missing codegen plugin"

https://github.com/dotansimha/graphql-code-generator/blob/e8bc671a0f4145e9a24436c86ab0d24f94e91725/packages/graphql-codegen-cli/src/plugins.ts#L21-L54

The above code isn’t a sufficient try-catch for what I just experienced. In my case, having freshly installed and inited everything I was encountering a message saying libraries that I did have installed weren’t installed, and I should try the list.

After digging with a debugger into the above lines I found that while pluginLoader() did return an error while looking for a plugin, it didn’t match the condition err.code !== 'MODULE_NOT_FOUND', which resulted in the above mentioned warning message logic.

However in reality, the error that was occurring was because an underlying library wasn’t the right version and had shipped with a bug! I never got to see this message because the catch is too strict.

[krainboltgreene]

That is the exact thing I’m describing, thanks for bringing receipts!

[patrickocoffeyo]

@krainboltgreene I recently ran into a similar issue using @graphql/codegen-typescript. The plugin loader was throwing an error with the code MODULE_NOT_FOUND, but when you do a little logging you can see that the real error is Error: Cannot find module '@babel/runtime/helpers/objectSpread2'. My temporary solution was to install @babel/runtime as a dev dependency, however if I get some time this week I’ll put together a PR.