fix(deps): update all non-major dependencies

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@babel/preset-typescript (source)	7.26.0 -> 7.27.0
@changesets/cli (source)	2.28.1 -> 2.29.2
@graphql-tools/wrap (source)	10.0.32 -> 10.0.35
@types/express (source)	5.0.0 -> 5.0.1
@types/node (source)	22.13.10 -> 22.15.3
@types/react (source)	19.0.11 -> 19.1.2
@typescript-eslint/eslint-plugin (source)	8.26.1 -> 8.31.1
@typescript-eslint/parser (source)	8.26.1 -> 8.31.1
esbuild	0.25.1 -> 0.25.3
eslint (source)	9.22.0 -> 9.25.1
graphql	16.10.0 -> 16.11.0
lint-staged	15.5.0 -> 15.5.1
next (source)	15.2.4 -> 15.3.1
react (source)	19.0.0 -> 19.1.0
react-dom (source)	19.0.0 -> 19.1.0
ts-jest (source)	29.2.6 -> 29.3.2
typescript (source)	5.8.2 -> 5.8.3

---

Release Notes

babel/babel (@​babel/preset-typescript)

v7.27.0

Compare Source

👓 Spec Compliance

• babel-generator, babel-parser
  • #​16977 Default importAttributesKeyword to with (@​JLHwung)

🚀 New Feature

• babel-helper-create-class-features-plugin, babel-traverse, babel-types
  • #​17169 Allow traverseFast to exit early (@​liuxingbaoyu)
• babel-parser, babel-types
  • #​17110 Add ImportAttributes to Standardized and move its parser test fixtures (@​JLHwung)
• babel-generator
  • #​17100 fix(babel-generator): add named export of generate function (@​vovkasm)
• babel-parser, babel-template
  • #​17149 Add allowYieldOutsideFunction to parser (@​liuxingbaoyu)
• babel-plugin-transform-typescript, babel-traverse
  • #​17102 feat: Add upToScope parameter to hasBinding (@​liuxingbaoyu)
• babel-parser
  • #​17082 Support ESTree AccessorProperty (@​JLHwung)
• babel-types
  • #​17162 feat(babel-types): Add support for BigInt literal conversion in valueToNode (@​ishchhabra)

🐛 Bug Fix

• babel-helper-create-class-features-plugin, babel-plugin-transform-class-properties
  • #​16816 fix: Class reference in type throws error (@​liuxingbaoyu)
• babel-traverse
  • #​17170 fix: Reset child scopes when scope.crawl() (@​liuxingbaoyu)
• babel-helpers, babel-preset-typescript, babel-runtime-corejs2, babel-runtime-corejs3, babel-runtime
  • #​17118 Fix: align behaviour to tsc rewriteRelativeImportExtensions (@​JLHwung)
• babel-cli
  • #​17182 fix: @babel/cli generates duplicate inline source maps (@​liuxingbaoyu)
• babel-plugin-transform-named-capturing-groups-regex, babel-types
  • #​17175 Generate computed proto key (@​JLHwung)

🏃‍♀️ Performance

• babel-types
  • #​16870 perf: Improve builders of @babel/types (@​liuxingbaoyu)
• babel-helper-create-regexp-features-plugin
  • #​17176 fix: improve duplicate named groups check (@​JLHwung)

changesets/changesets (@​changesets/cli)

v2.29.2

Compare Source

Patch Changes

• #​1636 f73f84a Thanks @​Netail! - Correctly resolve new changesets with since option when the .changeset directory is not directly in the git root

• Updated dependencies [f73f84a]:

  • @​changesets/read@​0.6.5
  • @​changesets/git@​3.0.4
  • @​changesets/get-release-plan@​4.0.10
  • @​changesets/apply-release-plan@​7.0.12

v2.29.1

Compare Source

v2.29.0

Compare Source

Minor Changes

• #​1470 29f34a3 Thanks @​JounQin! - Support scoped registries configured using package.json#publishConfig

graphql-hive/gateway (@​graphql-tools/wrap)

v10.0.35

Compare Source

Patch Changes

• Updated dependencies [c7ea2c5, 0af3485]:
  • @​graphql-tools/delegate@​10.2.17

v10.0.34

Compare Source

Patch Changes

• #​532 4e33933 Thanks @​EmrysMyrddin! - dependencies updates:

  • Updated dependency @whatwg-node/promise-helpers@^1.3.0 ↗︎ (from ^1.2.5, in dependencies)

• Updated dependencies [4e33933]:

  • @​graphql-tools/delegate@​10.2.16

v10.0.33

Compare Source

Patch Changes

• #​862 278618a Thanks @​ardatan! - dependencies updates:

  • Updated dependency @whatwg-node/promise-helpers@^1.2.5 ↗︎ (from ^1.0.0, in dependencies)

• Updated dependencies [278618a]:

  • @​graphql-tools/delegate@​10.2.15

typescript-eslint/typescript-eslint (@​typescript-eslint/eslint-plugin)

v8.31.1

Compare Source

🩹 Fixes

• eslint-plugin: [no-unnecessary-condition] downgrade fix to suggestion (#​11081)

❤️ Thank You

• Kirk Waiblinger @​kirkwaiblinger

You can read about our versioning strategy and releases on our website.

v8.31.0

Compare Source

🚀 Features

• eslint-plugin: [no-unnecessary-type-assertion] add option to ignore string const assertions (#​10979)

❤️ Thank You

• Nicolas Le Cam

You can read about our versioning strategy and releases on our website.

v8.30.1

Compare Source

🩹 Fixes

• eslint-plugin: fix mistake with eslintrc config generation (#​11072)

❤️ Thank You

• Kirk Waiblinger @​kirkwaiblinger

You can read about our versioning strategy and releases on our website.

v8.30.0

Compare Source

🚀 Features

• eslint-plugin: [no-explicit-any] suggest to replace keyof any with PropertyKey (#​11032)

🩹 Fixes

• eslint-plugin: [promise-function-async] use a different error message for functions with promise and non-promise types (#​10950)

❤️ Thank You

• Dima Barabash @​dbarabashh
• Ronen Amiel

You can read about our versioning strategy and releases on our website.

v8.29.1

Compare Source

🩹 Fixes

• eslint-plugin: [no-deprecated] report on deprecated imported variable used as property (#​10998)

❤️ Thank You

• Ronen Amiel

You can read about our versioning strategy and releases on our website.

v8.29.0

Compare Source

🚀 Features

• eslint-plugin: [prefer-nullish-coalescing] create ignoreIfStatements option (#​11000)

🩹 Fixes

• eslint-plugin: [no-array-constructor] remove optional chaining exemption (#​10963)
• eslint-plugin: support arbitrary extensions in definition files (#​10957)
• eslint-plugin: [prefer-for-of] fix false positive when using erasable type syntax within update expressions (#​10981)
• eslint-plugin: [use-unknown-in-catch-callback-variable] remove fixable property (#​10993)
• eslint-plugin: [no-unnecessary-condition] don't report on unnecessary optional array index access when noUncheckedIndexedAccess is enabled (#​10961)

❤️ Thank You

• Dima Barabash @​dbarabashh
• Kim Sang Du @​developer-bandi
• Olivier Zalmanski @​OlivierZal
• Ronen Amiel
• Yannick Decat @​mho22
• zyoshoka @​zyoshoka

You can read about our versioning strategy and releases on our website.

v8.28.0

Compare Source

🚀 Features

• eslint-plugin: [prefer-nullish-coalescing] support if statement assignment (??=) and fix several minor bugs (#​10861)

🩹 Fixes

• eslint-plugin: [no-unsafe-function-type] remove fixable property (#​10986)

❤️ Thank You

• Olivier Zalmanski @​OlivierZal
• Yannick Decat @​mho22

You can read about our versioning strategy and releases on our website.

v8.27.0

Compare Source

🚀 Features

• utils: support DeprecatedInfo for rule.meta.deprecated (#​10932)

❤️ Thank You

• ntnyq @​ntnyq

You can read about our versioning strategy and releases on our website.

typescript-eslint/typescript-eslint (@​typescript-eslint/parser)

v8.31.1

Compare Source

This was a version bump only for parser to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

v8.31.0

Compare Source

This was a version bump only for parser to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

v8.30.1

Compare Source

This was a version bump only for parser to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

v8.30.0

Compare Source

This was a version bump only for parser to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

v8.29.1

Compare Source

This was a version bump only for parser to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

v8.29.0

Compare Source

This was a version bump only for parser to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

v8.28.0

Compare Source

This was a version bump only for parser to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

v8.27.0

Compare Source

This was a version bump only for parser to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

evanw/esbuild (esbuild)

v0.25.3

Compare Source

• Fix lowered async arrow functions before super() (#​4141, #​4142)

  This change makes it possible to call an async arrow function in a constructor before calling super() when targeting environments without async support, as long as the function body doesn't reference this. Here's an example (notice the change from this to null):

  // Original code
  class Foo extends Object {
    constructor() {
      (async () => await foo())()
      super()
    }
  }
  
  // Old output (with --target=es2016)
  class Foo extends Object {
    constructor() {
      (() => __async(this, null, function* () {
        return yield foo();
      }))();
      super();
    }
  }
  
  // New output (with --target=es2016)
  class Foo extends Object {
    constructor() {
      (() => __async(null, null, function* () {
        return yield foo();
      }))();
      super();
    }
  }

  Some background: Arrow functions with the async keyword are transformed into generator functions for older language targets such as --target=es2016. Since arrow functions capture this, the generated code forwards this into the body of the generator function. However, JavaScript class syntax forbids using this in a constructor before calling super(), and this forwarding was problematic since previously happened even when the function body doesn't use this. Starting with this release, esbuild will now only forward this if it's used within the function body.

  This fix was contributed by @​magic-akari.

• Fix memory leak with --watch=true (#​4131, #​4132)

  This release fixes a memory leak with esbuild when --watch=true is used instead of --watch. Previously using --watch=true caused esbuild to continue to use more and more memory for every rebuild, but --watch=true should now behave like --watch and not leak memory.

  This bug happened because esbuild disables the garbage collector when it's not run as a long-lived process for extra speed, but esbuild's checks for which arguments cause esbuild to be a long-lived process weren't updated for the new --watch=true style of boolean command-line flags. This has been an issue since this boolean flag syntax was added in version 0.14.24 in 2022. These checks are unfortunately separate from the regular argument parser because of how esbuild's internals are organized (the command-line interface is exposed as a separate Go API so you can build your own custom esbuild CLI).

  This fix was contributed by @​mxschmitt.

• More concise output for repeated legal comments (#​4139)

  Some libraries have many files and also use the same legal comment text in all files. Previously esbuild would copy each legal comment to the output file. Starting with this release, legal comments duplicated across separate files will now be grouped in the output file by unique comment content.

• Allow a custom host with the development server (#​4110)

  With this release, you can now use a custom non-IP host with esbuild's local development server (either with --serve= for the CLI or with the serve() call for the API). This was previously possible, but was intentionally broken in version 0.25.0 to fix a security issue. This change adds the functionality back except that it's now opt-in and only for a single domain name that you provide.

  For example, if you add a mapping in your /etc/hosts file from local.example.com to 127.0.0.1 and then use esbuild --serve=local.example.com:8000, you will now be able to visit http://local.example.com:8000/ in your browser and successfully connect to esbuild's development server (doing that would previously have been blocked by the browser). This should also work with HTTPS if it's enabled (see esbuild's documentation for how to do that).

• Add a limit to CSS nesting expansion (#​4114)

  With this release, esbuild will now fail with an error if there is too much CSS nesting expansion. This can happen when nested CSS is converted to CSS without nesting for older browsers as expanding CSS nesting is inherently exponential due to the resulting combinatorial explosion. The expansion limit is currently hard-coded and cannot be changed, but is extremely unlikely to trigger for real code. It exists to prevent esbuild from using too much time and/or memory. Here's an example:

  a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{color:red}}}}}}}}}}}}}}}}}}}}

  Previously, transforming this file with --target=safari1 took 5 seconds and generated 40mb of CSS. Trying to do that will now generate the following error instead:

  ✘ [ERROR] CSS nesting is causing too much expansion
  
      example.css:1:60:
        1 │ a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{color:red}}}}}}}}}}}}}}}}}}}}
          ╵                                                             ^
  
    CSS nesting expansion was terminated because a rule was generated with 65536 selectors. This limit
    exists to prevent esbuild from using too much time and/or memory. Please change your CSS to use
    fewer levels of nesting.
  

• Fix path resolution edge case (#​4144)

  This fixes an edge case where esbuild's path resolution algorithm could deviate from node's path resolution algorithm. It involves a confusing situation where a directory shares the same file name as a file (but without the file extension). See the linked issue for specific details. This appears to be a case where esbuild is correctly following node's published resolution algorithm but where node itself is doing something different. Specifically the step LOAD_AS_FILE appears to be skipped when the input ends with ... This release changes esbuild's behavior for this edge case to match node's behavior.

• Update Go from 1.23.7 to 1.23.8 (#​4133, #​4134)

  This should have no effect on existing code as this version change does not change Go's operating system support. It may remove certain reports from vulnerability scanners that detect which version of the Go compiler esbuild uses, such as for CVE-2025-22871.

  As a reminder, esbuild's development server is intended for development, not for production, so I do not consider most networking-related vulnerabilities in Go to be vulnerabilities in esbuild. Please do not use esbuild's development server in production.

v0.25.2

Compare Source

• Support flags in regular expressions for the API (#​4121)

  The JavaScript plugin API for esbuild takes JavaScript regular expression objects for the filter option. Internally these are translated into Go regular expressions. However, this translation previously ignored the flags property of the regular expression. With this release, esbuild will now translate JavaScript regular expression flags into Go regular expression flags. Specifically the JavaScript regular expression /\.[jt]sx?$/i is turned into the Go regular expression `(?i)\.[jt]sx?$` internally inside of esbuild's API. This should make it possible to use JavaScript regular expressions with the i flag. Note that JavaScript and Go don't support all of the same regular expression features, so this mapping is only approximate.

• Fix node-specific annotations for string literal export names (#​4100)

  When node instantiates a CommonJS module, it scans the AST to look for names to expose via ESM named exports. This is a heuristic that looks for certain patterns such as exports.NAME = ... or module.exports = { ... }. This behavior is used by esbuild to "annotate" CommonJS code that was converted from ESM with the original ESM export names. For example, when converting the file export let foo, bar from ESM to CommonJS, esbuild appends this to the end of the file:

  // Annotate the CommonJS export names for ESM import in node:
  0 && (module.exports = {
    bar,
    foo
  });

  However, this feature previously didn't work correctly for export names that are not valid identifiers, which can be constructed using string literal export names. The generated code contained a syntax error. That problem is fixed in this release:

  // Original code
  let foo
  export { foo as "foo!" }
  
  // Old output (with --format=cjs --platform=node)
  ...
  0 && (module.exports = {
    "foo!"
  });
  
  // New output (with --format=cjs --platform=node)
  ...
  0 && (module.exports = {
    "foo!": null
  });

• Basic support for index source maps (#​3439, #​4109)

  The source map specification has an optional mode called index source maps that makes it easier for tools to create an aggregate JavaScript file by concatenating many smaller JavaScript files with source maps, and then generate an aggregate source map by simply providing the original source maps along with some offset information. My understanding is that this is rarely used in practice. I'm only aware of two uses of it in the wild: ClojureScript and Turbopack.

  This release provides basic support for indexed source maps. However, the implementation has not been tested on a real app (just on very simple test input). If you are using index source maps in a real app, please try this out and report back if anything isn't working for you.

  Note that this is also not a complete implementation. For example, index source maps technically allows nesting source maps to an arbitrary depth, while esbuild's implementation in this release only supports a single level of nesting. It's unclear whether supporting more than one level of nesting is important or not given the lack of available test cases.

  This feature was contributed by @​clyfish.

eslint/eslint (eslint)

v9.25.1

Compare Source

v9.25.0

Compare Source

v9.24.0

Compare Source

v9.23.0

Compare Source

graphql/graphql-js (graphql)

v16.11.0: 16.11.0

Compare Source

v16.11.0 (2025-04-26)

New Feature 🚀

• #​4363 Ensure we validate for using nullable variables in oneOf input fields (@​JoviDeCroock)
• #​4366 feat(execution): add max coercion errors option to execution context (@​cristunaranjo)

Bug Fix 🐞

• #​4367 fix(coerce-input-value): input object coercion rejects arrays (@​cristunaranjo)

Docs 📝

11 PRs were merged

• #​4310 First draft for upgrade guide to v17 (@​JoviDeCroock)
• #​4331 fix sidebar for documentation and /api-v16 (@​dimaMachina)
• #​4335 Add cspell exception (@​JoviDeCroock)
• #​4340 Improve flow of documentation around GraphiQL (@​benjie)
• #​4343 typofix: removes extra parenthesis from getting started code snippet (@​rabahalishah)
• #​4351 fixed wrong variable name (@​fto-dev)
• #​4352 docs(getting-started): promises current links (@​guspan-tanadi)
• #​4368 Update docs for execution options (@​JoviDeCroock)
• #​4369 Correct some syntax (@​JoviDeCroock)
• #​4372 Refactor every code-first example to leverage resolve (@​JoviDeCroock)
• #​4373 docs: Update getting-started.mdx (@​Shubhdeep12)

Polish 💅

• #​4312 Increase print/visit performance (@​JoviDeCroock)

Internal 🏠

4 PRs were merged

• #​4327 Add redirect for /api (@​JoviDeCroock)
• #​4377 Chore: bump setup-node (@​JoviDeCroock)
• #​4378 Change to gqlConf 2025 (@​JoviDeCroock)
• #​4379 Add missing parenthesis (@​benjie)

Committers: 8

• Benjie(@​benjie)
• Cris Naranjo (@​cristunaranjo)
• Dimitri POSTOLOV(@​dimaMachina)
• Fatih Ozdemir(@​fto-dev)
• Guspan Tanadi(@​guspan-tanadi)
• Jovi De Croock(@​JoviDeCroock)
• Rabah Ali Shah(@​rabahalishah)
• Shubhdeep Chhabra(@​Shubhdeep12)

lint-staged/lint-staged (lint-staged)

v15.5.1

Compare Source

Patch Changes

• #​1533 5d53534 Thanks @​iiroj! - Improve listing of staged files so that lint-staged doesn't crash when encountering an uninitialized submodule. This should result in less errors like:

  ✖ Failed to get staged files!
  

vercel/next.js (next)

v15.3.1

Compare Source

v15.3.0

Compare Source

v15.2.5

Compare Source

facebook/react (react)

v19.1.0

Compare Source

facebook/react (react-dom)

v19.1.0

Compare Source

kulshekhar/ts-jest (ts-jest)

v29.3.2

Compare Source

Bug Fixes

• fix: transpile js files from node_modules whenever Jest asks (968370e), closes #​4637

v29.3.1

Compare Source

Bug Fixes

• fix: allow isolatedModules mode to have ts.Program under Node16/Next (25157eb)
• fix: improve message for isolatedModules of ts-jest config (547eb6f)

v29.3.0

Compare Source

Features

• feat: support hybrid module values for isolatedModules: true (f372121)

Bug Fixes

• fix: set customConditions to undefined in TsCompiler (b091d70), closes #​4620

Code Refactoring

• refactor: remove manual version checker (89458fc)
• refactor: remove patching deps based on version checker (bac4c43)
• refactor: deprecate RawCompilerOptions interface (2b1b6cd)
• refactor: deprecate transform option isolatedModules (7dfef71)

microsoft/TypeScript (typescript)

v5.8.3

Compare Source

---

Configuration

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

🚦 Automerge: Enabled.

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