Skip to content

Update graphqlcodegenerator monorepo (major)#57

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/major-graphqlcodegenerator-monorepo
Open

Update graphqlcodegenerator monorepo (major)#57
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/major-graphqlcodegenerator-monorepo

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented Mar 18, 2023

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
@graphql-codegen/cli (source) 2.13.67.0.0 age confidence
@graphql-codegen/typescript (source) 2.7.46.0.1 age confidence
@graphql-codegen/typescript-operations (source) 2.5.46.0.2 age confidence

Release Notes

dotansimha/graphql-code-generator (@​graphql-codegen/cli)

v7.0.0

Compare Source

Major Changes
  • #​10496
    afaace6
    Thanks @​eddeee888! - BREAKING CHANGE: Update deps to latest, some
    only support ESM

    Node 20 support is dropped in this release. Node 22 comes with require() support for ESM, which
    means it's easier to integrate ES modules into applications. Therefore, it is safe to start using
    ESM-only packages.

    If you are a user, please upgrade to Node 22. If you are a lib maintainer and see ESM vs CJS
    issues when running Jest tests, try using Vitest.

  • #​10496
    afaace6
    Thanks @​eddeee888! - BREAKING CHANGE: Drop Node 20 support

  • #​10496
    afaace6
    Thanks @​eddeee888! - BREAKING CHANGE: Set noSilentErrors: true
    by default

    When multiple files match documents pattern, and there are syntax errors in some but not others,
    then the operations with errors are not included in the loaded documents list by default
    (noSilentErrors: false). This is annoying for users as there is no feedback loop during
    development.

    noSilentErrors: true is used as the default for Codegen users to make the feedback loop faster.
    It can still overriden in Codegen Config if desired.

Patch Changes

v6.3.1

Compare Source

Patch Changes
  • #​10737
    be85118
    Thanks @​eddeee888! - Fix issue where same SDL in different
    documents are ignored when handling documents vs externalDocuments

v6.3.0

Compare Source

Minor Changes
  • #​10659
    e65d303
    Thanks @​ikusakov2! - Add support for externalDocuments

    externalDocuments declares GraphQL documents that will be read but will not have type files
    generated for them. These documents are available to plugins for type resolution (e.g. fragment
    types), but no output files will be generated based on them. Accepts the same formats as
    documents.

    This config option is useful for monorepos where each project may want to generate types for its
    own documents, but some may need to read shared fragments from across projects.

Patch Changes

v6.2.1

Compare Source

Patch Changes
  • #​10618 e804925 Thanks @​PalmerTurley34! - Honor per-output preset importExtension and emitLegacyCommonJSImports config instead of always using the root config values.

v6.2.0

Compare Source

Minor Changes
Patch Changes

v6.1.3

Compare Source

Patch Changes

v6.1.2

Compare Source

Patch Changes
  • #​10590 e173e11 Thanks @​ya2s! - Fix GraphQL Config loading to forward nested extensions.codegen.config options
    when loading schemas/documents, matching codegen.ts behavior.

v6.1.1

Compare Source

Patch Changes
  • #​10569 8cb7d43 Thanks @​etr2460! - fix(graphql-codegen-cli): Don't hang when 0 CPUs are found

    Fixes generation when 0 CPUs are returned by os.cpus(), which occurs in sandbox environments.

v6.1.0

Compare Source

Minor Changes
Patch Changes

v6.0.2

Compare Source

Patch Changes

v6.0.1

Compare Source

Patch Changes
  • #​10468 cb1b9d9 Thanks @​eddeee888! - In watch mode, do not write output on failure

    Previously, on partial or full failure, watch mode still write to output. However, since the output'd be an empty array, it will then call removeStaleFiles internally to remove all previously generated files.

    This patch puts a temporary fix to avoid writing output on any failure to fix the described behaviour.

    This also means the config.allowPartialOutputs does not work in watch mode for now.

v6.0.0

Compare Source

Major Changes
Patch Changes

v5.0.7

Compare Source

Patch Changes

v5.0.6

Compare Source

Patch Changes

v5.0.5

Compare Source

Patch Changes

v5.0.4

Compare Source

Patch Changes

v5.0.3

Compare Source

Patch Changes

v5.0.2

Compare Source

Patch Changes

v5.0.1

Compare Source

Patch Changes

v5.0.0

Compare Source

Major Changes
Patch Changes

v4.0.1

Compare Source

Patch Changes

v4.0.0

Compare Source

Major Changes
Patch Changes

v3.3.1

Compare Source

Patch Changes

v3.3.0

Compare Source

Minor Changes
  • #​9151 b7dacb21f Thanks @​'./user/schema.mappers#UserMapper',! - Add watchPattern config option for generates sections.

    By default, watch mode automatically watches all GraphQL schema and document files. This means when a change is detected, Codegen CLI is run.

    A user may want to run Codegen CLI when non-schema and non-document files are changed. Each generates section now has a watchPattern option to allow more file patterns to be added to the list of patterns to watch.

    In the example below, mappers are exported from schema.mappers.ts files. We want to re-run Codegen if the content of *.mappers.ts files change because they change the generated types file. To solve this, we can add mapper file patterns to watch using the glob pattern used for schema and document files.

    // codegen.ts
    const config: CodegenConfig = {
      schema: 'src/schema/**/*.graphql',
      generates: {
        'src/schema/types.ts': {
          plugins: ['typescript', 'typescript-resolvers'],
          config: {
            mappers: {
    
              Book: './book/schema.mappers#BookMapper',
            },
          }
          watchPattern: 'src/schema/**/*.mappers.ts', // Watches mapper files in `watch` mode. Use an array for multiple patterns e.g. `['src/*.pattern1.ts','src/*.pattern2.ts']`
        },
      },
    };

    Then, run Codegen CLI in watch mode:

    yarn graphql-codegen --watch

    Now, updating *.mappers.ts files re-runs Codegen! 🎉

    Note: watchPattern is only used in watch mode i.e. running CLI with --watch flag.

Patch Changes

v3.2.2

Compare Source

Patch Changes

v3.2.1

Compare Source

Patch Changes

v3.2.0

Compare Source

Minor Changes
Patch Changes

v3.1.0

Compare Source

Minor Changes
  • #​8893 a118c307a Thanks @​n1ru4l! - It is no longer mandatory to declare an empty plugins array when using a preset

  • #​8723 a3309e63e Thanks @​kazekyo! - Introduce a new feature called DocumentTransform.

    DocumentTransform is a functionality that allows you to modify documents before they are processed by plugins. You can use functions passed to the documentTransforms option to make changes to GraphQL documents.

    To use this feature, you can write documentTransforms as follows:

    import type { CodegenConfig } from '@​graphql-codegen/cli'
    
    const config: CodegenConfig = {
      schema: 'https://localhost:4000/graphql',
      documents: ['src/**/*.tsx'],
      generates: {
        './src/gql/': {
          preset: 'client',
          documentTransforms: [
            {
              transform: ({ documents }) => {
                // Make some changes to the documents
                return documents
              }
            }
          ]
        }
      }
    }
    export default config

    For instance, to remove a @localOnlyDirective directive from documents, you can write the following code:

    import type { CodegenConfig } from '@​graphql-codegen/cli'
    import { visit } from 'graphql'
    
    const config: CodegenConfig = {
      schema: 'https://localhost:4000/graphql',
      documents: ['src/**/*.tsx'],
      generates: {
        './src/gql/': {
          preset: 'client',
          documentTransforms: [
            {
              transform: ({ documents }) => {
                return documents.map(documentFile => {
                  documentFile.document = visit(documentFile.document, {
                    Directive: {
                      leave(node) {
                        if (node.name.value === 'localOnlyDirective') return null
                      }
                    }
                  })
                  return documentFile
                })
              }
            }
          ]
        }
      }
    }
    export default config

    DocumentTransform can also be specified by file name. You can create a custom file for a specific transformation and pass it to documentTransforms.

    Let's create the document transform as a file:

    module.exports = {
      transform: ({ documents }) => {
        // Make some changes to the documents
        return documents
      }
    }

    Then, you can specify the file name as follows:

    import type { CodegenConfig } from '@​graphql-codegen/cli'
    
    const config: CodegenConfig = {
      schema: 'https://localhost:4000/graphql',
      documents: ['src/**/*.tsx'],
      generates: {
        './src/gql/': {
          preset: 'client',
          documentTransforms: ['./my-document-transform.js']
        }
      }
    }
    export default config
Patch Changes

Note

PR body was truncated to here.


Configuration

📅 Schedule: (UTC)

  • 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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


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

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from 093b3fb to 1ebbaec Compare April 17, 2023 12:34
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from 1ebbaec to 1172517 Compare May 28, 2023 11:22
@renovate renovate Bot changed the title Update graphqlcodegenerator monorepo to v3 (major) Update graphqlcodegenerator monorepo to v4 (major) May 28, 2023
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from 1172517 to 2bb652f Compare June 1, 2023 20:02
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from 2bb652f to bade1ea Compare June 19, 2023 10:37
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from bade1ea to 41aa53f Compare July 25, 2023 10:17
@renovate renovate Bot changed the title Update graphqlcodegenerator monorepo to v4 (major) Update graphqlcodegenerator monorepo (major) Jul 25, 2023
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from 41aa53f to 247f04f Compare February 6, 2024 15:17
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 2 times, most recently from 3d434c7 to f29b7e1 Compare February 22, 2024 21:43
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from f29b7e1 to 8d76439 Compare May 17, 2024 17:05
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 2 times, most recently from 987d941 to f1a5d4d Compare July 2, 2024 10:58
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from f1a5d4d to 2b5d04f Compare October 7, 2024 16:01
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from 2b5d04f to a5efa1c Compare October 28, 2024 13:40
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from a5efa1c to 7fa9341 Compare November 22, 2024 21:43
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from 7fa9341 to b4f2a37 Compare January 28, 2025 12:35
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 2 times, most recently from c5c7312 to 3fef56d Compare February 19, 2025 17:07
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from 3fef56d to e7f036b Compare February 23, 2025 21:39
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from e7f036b to f34881e Compare March 27, 2025 12:38
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from f34881e to d2381ef Compare May 6, 2025 17:03
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from d2381ef to be2c018 Compare June 6, 2025 19:13
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 2 times, most recently from 0bfde76 to c86f0a5 Compare August 13, 2025 11:48
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from c86f0a5 to 63123b0 Compare August 19, 2025 17:38
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from 63123b0 to aff8f22 Compare August 31, 2025 14:17
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from aff8f22 to 0b56b3c Compare September 7, 2025 21:58
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 2 times, most recently from 93bcd43 to 9d21e67 Compare September 29, 2025 16:53
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 2 times, most recently from 1067a3b to 33239c5 Compare November 20, 2025 13:53
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 2 times, most recently from 1794ed4 to a3feacc Compare December 3, 2025 19:17
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from a3feacc to 563166f Compare December 18, 2025 14:42
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from 563166f to 2e0abff Compare December 31, 2025 13:08
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 2 times, most recently from dd40ed0 to 5efa217 Compare January 11, 2026 13:57
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 2 times, most recently from f514e5d to 03af106 Compare January 23, 2026 18:30
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from 03af106 to 0c537df Compare February 2, 2026 14:58
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 3 times, most recently from 696e3f7 to ef77737 Compare February 18, 2026 15:05
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from ef77737 to d00810a Compare February 22, 2026 17:39
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 4 times, most recently from b0b6a72 to d9e5336 Compare March 12, 2026 13:00
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from d9e5336 to 3e21693 Compare March 13, 2026 15:21
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 2 times, most recently from bba80b1 to 981c11a Compare April 8, 2026 14:55
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 2 times, most recently from dc4a7aa to 9d8996a Compare April 18, 2026 18:42
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 2 times, most recently from 713aebc to 26d7dbe Compare April 30, 2026 16:51
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 2 times, most recently from e1b995c to 1ba9faf Compare May 9, 2026 12:34
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from 1ba9faf to 1f71d22 Compare May 12, 2026 17:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants