fix(deps): update dependency graphql-config to v4 - autoclosed

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
graphql-config (source)	3.4.1 -> 4.5.0

---

Release Notes

kamilkisiela/graphql-config

v4.5.0

Compare Source

Minor Changes

• 9e4f453 Thanks @​kamilkisiela! - Support ESM and .mts/.cts config extensions

v4.4.1

Compare Source

Patch Changes

• #​1245 bad5090 Thanks @​B2o5T! - fix peerDependenciesMeta was not included in package.json

v4.4.0

Compare Source

Minor Changes

• #​1189 ab2ad6d Thanks @​B2o5T! - add cosmiconfig-toml-loader to peerDependenciesMeta

• #​1171 b52dc1b Thanks @​B2o5T! - move cosmiconfig-typescript-loader in peerDependencyMeta

v4.3.6

Compare Source

Patch Changes

• #​1149 a12f394 Thanks @​charlypoly! - conflict with codegen also using TypeScriptLoader(), causing a double ts-node register.

v4.3.5

Compare Source

Patch Changes

• #​1126 cc781c4 Thanks @​n1ru4l! - dependencies updates:

  • Updated dependency cosmiconfig-typescript-loader@^4.0.0 ↗︎ (from ^3.1.0, in dependencies)

v4.3.4

Compare Source

Patch Changes

• #​1103 2c568f1 Thanks @​renovate! - dependencies updates:

  • Added dependency tslib@^2.4.0 ↗︎ (to dependencies)

• #​1103 2c568f1 Thanks @​renovate! - Proper ESM/CJS support on Node.js

v4.3.3

Compare Source

Patch Changes

• cd7747e: bump cosmiconfig-typescript-loader to resolve errors with esm loading

v4.3.2

Compare Source

Patch Changes

• f74d648: fix: change to maintained version of cosmiconfig-typescript-loader

v4.3.1

Compare Source

Patch Changes

• 44eec8d: Add workaround for default import of typescript config loader to fix ESM support

v4.3.0

Compare Source

Minor Changes

• aaccd04: feat: improve types to fix JSON schema when schema is passed like object with headers

Patch Changes

• 18d07fd: fix: rollback GraphQLConfig.projects to empty object instead Object.create(null)

v4.2.0

Minor Changes

• 0636e9a: feat: support graphql.config.cjs config
• 55f078a: feat: update graphql-tools packages

Patch Changes

• fix: update minimatch dependency

Thanks to @​bfanger for his first contribution 0636e9a

vNEXT

v4.0.2

• Update range of @graphql-tools/merge dependency to include v7 and v8

v4.0.1

• Updated dependencies of graphql-tools to latest, to address issues related to documents loading.

v4.0.0

‼️ ‼️ ‼️ BREAKING CHANGE ‼️ ‼️ ‼️

Dropped Node 10 support, due to the need to support ESM in this package.

‼️ ‼️ ‼️ BREAKING CHANGE ‼️ ‼️ ‼️

The signature of Loader has been changed in graphql-tools, to allow more flexibility.

If you are using graphql-config with extensions, then the Extension you are using needs to adjust to the new return value of Loader signature that returns Source[] | null instead of Source. (see: https://github.com/kamilkisiela/graphql-config/issues/716)

Other changes:

• ESM Support
• Update dependencies of graphql-tools.

v3.4.0

Note: A breaking chnage snuk into that version, please see v4.

• Update dependencies of graphql-tools.

v3.3.0

• Add support for loading the config from package.json #​693 by @​ionut-botizan

v3.2.0

• Allow custom options for loadSchema #​593

v3.1.0

• TOML and TypeScript loaders #​595 by @​acao
• Add ability to override default loaders #​583 by @​danielrearden

v3.0.2

• Fix missing types #​542

v3.0.1

• use GraphQL Toolkit v0.10.6

v3.0.0

Read the Migration chapter

• Support GraphQL v15
• Support CommonJS and ES Modules
• Support environment variables with default values
• Match a file with a GraphQL Project
• JSON Schema
• New Extensions system with Loaders
• includes and excludes becomes include and exlude
• New field documents - defines GraphQL Operations and Fragments
• Broader spectrum of config file names
• Support custom config name
• Synchonous version
• Support legacy #​437
• Extensions capable of modifying GraphQL Schemas #​463

Prior to v3

Changes: https://github.com/kamilkisiela/graphql-config/releases

v4.0.2

Compare Source

• Update range of @graphql-tools/merge dependency to include v7 and v8

v4.0.1

Compare Source

• Updated dependencies of graphql-tools to latest, to address issues related to documents loading.

v4.0.0

Compare Source

‼️ ‼️ ‼️ BREAKING CHANGE ‼️ ‼️ ‼️

Dropped Node 10 support, due to the need to support ESM in this package.

‼️ ‼️ ‼️ BREAKING CHANGE ‼️ ‼️ ‼️

The signature of Loader has been changed in graphql-tools, to allow more flexibility.

If you are using graphql-config with extensions, then the Extension you are using needs to adjust to the new return value of Loader signature that returns Source[] | null instead of Source. (see: https://github.com/kamilkisiela/graphql-config/issues/716)

Other changes:

• ESM Support
• Update dependencies of graphql-tools.

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[guimochila]

Any reason why this PR has not been merged? @Urigo.

[Urigo]

We are in the process of redefining what GraphQL CLI is.
With all the new changes in https://github.com/urigo/graphql-mesh and in https://github.com/dotansimha/graphql-yoga, we are thinking of maybe extracting their CLI functionality into this tool.
We are still in the process so I think it might take a bit longer, I don't have a timeline yet.
What are you using GraphQL CLI for? Until what I mentioned happens, I would recommend using the CLIs of the individual tools as they are more up to date

[guimochila]

I am using to fetch graphql schemas from server and convert to typescript. First time I am reading about graphql-mesh, I will check it out too.

[Urigo]

@guimochila do you mean you are doing it using https://graphql-code-generator.com/ ?
If so, you can use https://graphql-code-generator.com 's own CLI

[guimochila]

@Urigo you are totally right! I have just switched to https://graphql-code-generator.com/ 's own CLI. Thank you for the information.

[felipeptcho]

@Urigo I can use https://graphql-code-generator.com/, but it has its own configuration file. For me, it was very interesting the idea of having just one GraphQL config file for all tools. That's why I'm still waiting for this PR to be merged.

[Urigo]

@felipeptcho you can use Codegen with GraphQL Config instead of it's own config.
All you need to do is to install both libraries.
You don't need graphql-cli for that: https://www.graphql-code-generator.com/docs/config-reference/codegen-config#other-ways-to-provide-configuration
Actually once you do that, maybe you can help us and contribute a recipe of how to use both to the docs of Codegen and Config's websites?