fix(deps): update all non-major dependencies

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@apollo/server (source)	^4.11.0 -> ^4.11.2
@babel/cli (source)	^7.25.7 -> ^7.25.9
@babel/code-frame (source)	^8.0.0-alpha.12 -> ^8.0.0-alpha.13
@babel/core (source)	^7.25.8 -> ^7.26.0
@babel/eslint-parser (source)	^7.25.8 -> ^7.25.9
@babel/plugin-transform-runtime (source)	^7.25.7 -> ^7.25.9
@babel/preset-env (source)	^7.25.8 -> ^7.26.0
@babel/preset-react (source)	^7.25.7 -> ^7.25.9
@babel/preset-typescript (source)	^7.25.7 -> ^7.26.0
@babel/register (source)	^7.25.7 -> ^7.25.9
@babel/runtime (source)	^7.25.7 -> ^7.26.0
@chakra-ui/react (source)	^2.10.2 -> ^2.10.4
@eslint/compat	^1.2.0 -> ^1.2.3
@reduxjs/toolkit (source)	^2.2.8 -> ^2.3.0
@rjsf/core	^5.21.2 -> ^5.22.4
@rjsf/utils	^5.21.2 -> ^5.22.4
@rjsf/validator-ajv8	^5.21.2 -> ^5.22.4
@storybook/addon-essentials (source)	^8.3.5 -> ^8.4.4
@storybook/addon-interactions (source)	^8.3.5 -> ^8.4.4
@storybook/addon-links (source)	^8.3.5 -> ^8.4.4
@storybook/addon-onboarding (source)	^8.3.5 -> ^8.4.4
@storybook/blocks (source)	^8.3.5 -> ^8.4.4
@storybook/react (source)	^8.3.5 -> ^8.4.4
@storybook/react-webpack5 (source)	^8.3.5 -> ^8.4.4
@storybook/test (source)	^8.3.5 -> ^8.4.4
@testing-library/jest-dom	^6.5.0 -> ^6.6.3
@types/chrome (source)	^0.0.278 -> ^0.0.283
@types/jest (source)	^29.5.13 -> ^29.5.14
@types/lodash (source)	^4.17.10 -> ^4.17.13
@types/node (source)	^20.16.11 -> ^20.17.6
@types/react (source)	^18.3.11 -> ^18.3.12
@typescript-eslint/eslint-plugin (source)	^8.9.0 -> ^8.14.0
@typescript-eslint/parser (source)	^8.9.0 -> ^8.14.0
electron	^31.7.0 -> ^31.7.5
eslint-plugin-jest	^28.8.3 -> ^28.9.0
eslint-plugin-react	^7.37.1 -> ^7.37.2
framer-motion	^11.11.8 -> ^11.11.17
globals	^15.11.0 -> ^15.12.0
html-webpack-plugin	^5.6.0 -> ^5.6.3
nanoid	^5.0.7 -> ^5.0.8
pnpm (source)	9.12.1 -> 9.13.2
react-router-dom (source)	^6.27.0 -> ^6.28.0
react-select (source)	^5.8.1 -> ^5.8.3
selenium-webdriver (source)	^4.25.0 -> ^4.26.0
socketcluster-client (source)	^19.2.2 -> ^19.2.3
socketcluster-server	^19.1.0 -> ^19.1.1
storybook (source)	^8.3.5 -> ^8.4.4
typescript-eslint (source)	^8.9.0 -> ^8.14.0
webpack	^5.95.0 -> ^5.96.1

---

Release Notes

apollographql/apollo-server (@​apollo/server)

v4.11.2

Compare Source

(No change; there is a change to the @apollo/server-integration-testsuite used to test integrations, and the two packages always have matching versions.)

v4.11.1

Compare Source

Patch Changes

• #​7952 bb81b2c Thanks @​glasser! - Upgrade dependencies so that automated scans don't detect a vulnerability.

  @apollo/server depends on express which depends on cookie. Versions of express older than v4.21.1 depend on a version of cookie vulnerable to CVE-2024-47764. Users of older express versions who call res.cookie() or res.clearCookie() may be vulnerable to this issue.

  However, Apollo Server does not call this function directly, and it does not expose any object to user code that allows TypeScript users to call this function without an unsafe cast.

  The only way that this direct dependency can cause a vulnerability for users of Apollo Server is if you call startStandaloneServer with a context function that calls Express-specific methods such as res.cookie() or res.clearCookies() on the response object, which is a violation of the TypeScript types provided by startStandaloneServer (which only promise that the response object is a core Node.js http.ServerResponse rather than the Express-specific subclass). So this vulnerability can only affect Apollo Server users who use unsafe JavaScript or unsafe as typecasts in TypeScript.

  However, this upgrade will at least prevent vulnerability scanners from alerting you to this dependency, and we encourage all Express users to upgrade their project's own express dependency to v4.21.1 or newer.

babel/babel (@​babel/cli)

v7.25.9

Compare Source

🐛 Bug Fix

• babel-parser, babel-template, babel-types
  • #​16905 fix: Keep type annotations in syntacticPlaceholders mode (@​liuxingbaoyu)
• babel-helper-compilation-targets, babel-preset-env
  • #​16907 fix: support BROWSERSLIST{,_CONFIG} env (@​JLHwung)
• Other
  • #​16884 Analyze ClassAccessorProperty to prevent the no-undef rule (@​victorenator)

🏠 Internal

• babel-helper-transform-fixture-test-runner
  • #​16914 remove test options flaky (@​JLHwung)

🏃‍♀️ Performance

• babel-parser, babel-types
  • #​16918 perf: Make VISITOR_KEYS etc. faster to access (@​liuxingbaoyu)

babel/babel (@​babel/code-frame)

v8.0.0-alpha.13

Compare Source

v8.0.0-alpha.13 (2024-10-25)

In addition to the changelog below, this release includes changes from v7.25.1 to v7.26.0

💥 Breaking Change

• babel-generator, babel-parser, babel-plugin-transform-typescript, babel-traverse, babel-types
  • #​16731 Add TSClassImplements|TSInterfaceHeritage and rename TsExpressionWithTypeArguments in Babel 8 (@​liuxingbaoyu)
• babel-generator, babel-parser, babel-plugin-proposal-pipeline-operator, babel-plugin-syntax-pipeline-operator, babel-standalone
  • #​16801 [Babel 8] Remove minimal,smart option of Pipeline Operator (@​liuxingbaoyu)
• babel-parser
  • #​16813 [Flow] Drop support for annotations inside array patterns (@​nicolo-ribaudo)
• babel-plugin-transform-class-static-block, babel-plugin-transform-destructuring, babel-plugin-transform-spread, babel-traverse
  • #​16705 [Babel 8] Remove some Scope methods (@​liuxingbaoyu)
• babel-generator, babel-parser, babel-plugin-proposal-import-wasm-source, babel-template, babel-types
  • #​16770 Remove importAssertions parser plugin (@​nicolo-ribaudo)
• babel-generator, babel-parser, babel-standalone
  • #​16808 Remove importReflection parser plugin (@​nicolo-ribaudo)
• babel-generator, babel-traverse, babel-types
  • #​16807 [Babel 8] Remove DecimalLiteral AST (@​liuxingbaoyu)
• babel-generator, babel-parser, babel-plugin-proposal-destructuring-private, babel-plugin-syntax-decimal, babel-standalone
  • #​16741 [Babel 8] Remove decimal from parser (@​liuxingbaoyu)
• babel-generator, babel-parser, babel-types
  • #​16733 [Babel 8] Split typeParameter of TSMappedType (@​liuxingbaoyu)
• babel-plugin-proposal-async-do-expressions, babel-traverse
  • #​16655 Remove some NodePath methods (@​liuxingbaoyu)

🚀 New Feature

• babel-parser, babel-plugin-syntax-flow, babel-preset-typescript
  • #​16792 [Babel 8] Remove enums option of flow plugin (@​liuxingbaoyu)

🐛 Bug Fix

• babel-core
  • #​16925 Only parse # as comment in .babelignore at line start (@​nicolo-ribaudo)
• babel-template, babel-types
  • #​16830 fix: ObjectPattern used as id inside for-of (@​coderaiser)
• babel-plugin-transform-async-generator-functions, babel-plugin-transform-block-scoped-functions, babel-plugin-transform-block-scoping
  • #​16398 Refactor transform-block-scoped-function (@​liuxingbaoyu)
• babel-helper-transform-fixture-test-runner, babel-node
  • #​16706 [babel 8] Align @babel/node args parsing to Node.js (@​nicolo-ribaudo)
• babel-parser
  • #​16668 [Babel 8] Fix spelling of error code (@​liuxingbaoyu)

💅 Polish

• babel-core
  • #​16836 [Babel 8] fix: Throwing exceptions synchronously (@​liuxingbaoyu)

🏠 Internal

• babel-generator, babel-helper-create-class-features-plugin, babel-helper-module-transforms, babel-plugin-proposal-destructuring-private, babel-plugin-transform-destructuring, babel-plugin-transform-modules-commonjs, babel-plugin-transform-object-rest-spread, babel-plugin-transform-parameters, babel-traverse, babel-types
  • #​16817 Remove BABEL_TYPES_8_BREAKING flag and enable it by default (@​liuxingbaoyu)
• Every package
  • #​16800 [babel 8] Require Node.js ^18.20.0 || ^20.17.0 || >=22.8.0 (@​nicolo-ribaudo)
• babel-generator, babel-parser, babel-plugin-bugfix-v8-spread-parameters-in-optional-chaining, babel-plugin-syntax-typescript, babel-plugin-transform-class-properties, babel-plugin-transform-modules-commonjs, babel-plugin-transform-private-methods, babel-plugin-transform-unicode-sets-regex, babel-traverse
  • #​16572 Clean all always enabled parser plugins (@​liuxingbaoyu)

Committers: 13

• Adrian (@​nerodesu017)
• Babel Bot (@​babel-bot)
• Dylan Piercey (@​DylanPiercey)
• Huáng Jùnliàng (@​JLHwung)
• Nicolò Ribaudo (@​nicolo-ribaudo)
• Timofei Iatsenko (@​timofei-iatsenko)
• Viktar Vaŭčkievič (@​victorenator)
• @​j4k0xb
• @​keiseiTi
• @​liuxingbaoyu
• coderaiser (@​coderaiser)
• fisker Cheung (@​fisker)
• hwook (@​YuHyeonWook)

babel/babel (@​babel/core)

v7.26.0

Compare Source

v7.25.9

Compare Source

🐛 Bug Fix

• babel-parser, babel-template, babel-types
  • #​16905 fix: Keep type annotations in syntacticPlaceholders mode (@​liuxingbaoyu)
• babel-helper-compilation-targets, babel-preset-env
  • #​16907 fix: support BROWSERSLIST{,_CONFIG} env (@​JLHwung)
• Other
  • #​16884 Analyze ClassAccessorProperty to prevent the no-undef rule (@​victorenator)

🏠 Internal

• babel-helper-transform-fixture-test-runner
  • #​16914 remove test options flaky (@​JLHwung)

🏃‍♀️ Performance

• babel-parser, babel-types
  • #​16918 perf: Make VISITOR_KEYS etc. faster to access (@​liuxingbaoyu)

eslint/rewrite (@​eslint/compat)

v1.2.3

Compare Source

v1.2.2

Compare Source

v1.2.1

Compare Source

reduxjs/redux-toolkit (@​reduxjs/toolkit)

v2.3.0

Compare Source

This feature release adds a new RTK Query upsertQueryEntries util to batch-upsert cache entries more efficiently, passes through additional values for use in prepareHeaders, and exports additional TS types around query options and selectors.

Changelog

upsertQueryEntries

RTK Query already had an upsertQueryData thunk that would upsert a single cache entry. However, some users wanted to upsert many cache entries (potentially hundreds or thousands), and found that upsertQueryData had poor performance in those cases. This is because upsertQueryData runs the full async request handling sequence, including dispatching both pending and fulfilled actions, each of which run the main reducer and update store subscribers. That means there's 2N store / UI updates per item, so upserting hundreds of items becomes extremely perf-intensive.

RTK Query now includes an api.util.upsertQueryEntries action that is meant to handle the batched upsert use case more efficiently. It's a single synchronous action that accepts an array of many {endpointName, arg, value} entries to upsert. This results in a single store update, making this vastly better for performance vs many individual upsertQueryData calls.

We see this as having two main use cases. The first is prefilling the cache with data retrieved from storage on app startup (and it's worth noting that upsertQueryEntries can accept entries for many different endpoints as part of the same array).

The second is to act as a "pseudo-normalization" tool. RTK Query is not a "normalized" cache. However, there are times when you may want to prefill other cache entries with the contents of another endpoint, such as taking the results of a getPosts list endpoint response and prefilling the individual getPost(id) endpoint cache entries, so that components that reference an individual item endpoint already have that data available.

Currently, you can implement the "pseudo-normalization" approach by dispatching upsertQueryEntries in an endpoint lifecycle, like this:

const api = createApi({
  endpoints: (build) => ({
    getPosts: build.query<Post[], void>({
      query: () => '/posts',
      async onQueryStarted(_, { dispatch, queryFulfilled }) {
        const res = await queryFulfilled
        const posts = res.data

        // Pre-fill the individual post entries with the results
        // from the list endpoint query
        dispatch(
          api.util.upsertQueryEntries(
            posts.map((post) => ({
              endpointName: 'getPost',
              arg: { id: post.id },
              value: post,
            })),
          ),
        )
      },
    }),
    getPost: build.query<Post, Pick<Post, 'id'>>({
      query: (post) => `post/${post.id}`,
    }),
  }),
})

Down the road we may add a new option to query e

[changeset-bot]

⚠️ No Changeset found

Latest commit: b149c25

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR