graphql-codegen/cli@2.16.4 needs ts-node

[numb86]

Which packages are impacted by your issue?

@graphql-codegen/cli

Describe the bug

Dependency for graphql-codegen/cli@2.16.4 x is incorrect.

Your Example Website or App

should occur in all environments.

Steps to Reproduce the Bug or Issue

$ mkdir foo
$ cd foo
$ yarn init -y
$ yarn add graphql@latest
$ yarn add @graphql-codegen/cli@2.16.4
$ yarn graphql-codegen

Error: Cannot find module 'ts-node'

Expected behavior

no error

Screenshots or Videos

No response

Platform

Platform doesn't matter

Codegen Config File

No response

Additional context

No response

[isoppp]

FYI: graphql-config seems to remove ts-node dependency in v4.4.0
kamilkisiela/graphql-config@v4.3.6...v4.4.0
https://github.com/dotansimha/graphql-code-generator/blob/master/packages/graphql-codegen-cli/package.json#L65

[jbsmith731]

Can confirm downgrading to 2.16.3 resolves the error

[ffxsam]

Side note: simple testing could've prevented a broken release from going out to a highly-used npm package (1.4 million downloads per week).

[hussein-jaban]

I just yarn add ts-node it worked.

[n1ru4l]

This was caused by a minor bump that should have been a major bump within graphql-config.
I am right now working on reverting and releasing a patch version for graphql-config that will solve this.

In the meantime, the solutions mentioned in #8814 (comment) and #8814 (comment) work as temporary workarounds.

Please also note that ts-node is a peer dependency of codegen: #8779

The documentation does currently not reflect that

[n1ru4l]

Okay, #8865 moved ts-node from peer dependencies to dependencies! I will release new versions shortly. Sorry for the inconvenience.

Regarding #8814 (comment)
we will be moving to pnpm soon, which will make these kinds of dependency chain issues easier to track.

Any other additional smoke tets contribution would be highly appreciated.

[n1ru4l]

@graphql-codegen/cli@2.16.5

got released.

[vladshcherbin]

@n1ru4l thanks for taking care of it! 🙌