Sourced from @​reduxjs/toolkit's releases.

v2.9.0

This feature release rewrites RTK Query's internal subscription and polling systems and the useStableQueryArgs hook for better perf, adds automatic AbortSignal handling to requests still in progress when a cache entry is removed, fixes a bug with the transformResponse option for queries, adds a new builder.addAsyncThunk method, and fixes assorted other issues.

Changelog

RTK Query Performance Improvements

We had reports that RTK Query could get very slow when there were thousands of subscriptions to the same cache entry. After investigation, we found that the internal polling logic was attempting to recalculate the minimum polling time after every new subscription was added. This was highly inefficient, as most subscriptions don't change polling settings, and it required repeated O(n) iteration over the growing list of subscriptions. We've rewritten that logic to debounce the update check and ensure a max of one polling value update per tick for the entire API instance.

Related, while working on the request abort changes, testing showed that use of plain Records to hold subscription data was inefficient because we have to iterate keys to check size. We've rewritten the subscription handling internals to use Maps instead, as well as restructuring some additional checks around in-flight requests.

These two improvements drastically improved runtime perf for the thousands-of-subscriptions-one-cache-entry repro, eliminating RTK methods as visible hotspots in the perf profiles. It likely also improves perf for general usage as well.

We've also changed the implementation of our internal useStableQueryArgs hook to avoid calling serializeQueryArgs on its value, which can avoid potential perf issues when a query takes a very large object as its cache key.

[!NOTE] The internal logic switched from serializing the query arg to doing reference checks on nested values. This means that if you are passing a non-POJO value in a query arg, such as useSomeQuery({a: new Set()}), and you have refetchOnMountOrArgChange enabled, this will now trigger refeteches each time as the Set references are now considered different based on equality instead of serialization.

Abort Signal Handling on Cleanup

We've had numerous requests over time for various forms of "abort in-progress requests when the data is no longer needed / params change / component unmounts / some expensive request is taking too long". This is a complex topic with multiple potential use cases, and our standard answer has been that we don't want to abort those requests - after all, cache entries default to staying in memory for 1 minute after the last subscription is removed, so RTKQ's cache can still be updated when the request completes. That also means that it doesn't make sense to abort a request "on unmount".

However, it does then make sense to abort an in-progress request if the cache entry itself is removed. Given that, we've updated our cache handling to automatically call the existing resPromise.abort() method in that case, triggering the AbortSignal attached to the baseQuery. The handling at that point depends on your app - fetchBaseQuery should handle that, a custom baseQuery or queryFn would need to listen to the AbortSignal.

We do have an open issue asking for further discussions of potential abort / cancelation use cases and would appreciate further feedback.

New Options

The builder callback used in createReducer and createSlice.extraReducers now has builder.addAsyncThunk available, which allows handling specific actions from a thunk in the same way that you could define a thunk inside createSlice.reducers:

        const slice = createSlice({
          name: 'counter',
          initialState: {
            loading: false,
            errored: false,
            value: 0,
          },
          reducers: {},
          extraReducers: (builder) =>
            builder.addAsyncThunk(asyncThunk, {
              pending(state) {
                state.loading = true
              },
              fulfilled(state, action) {
                state.value = action.payload
              },
              rejected(state) {
                state.errored = true
              },
</tr></table> 

... (truncated)

• 98c54c6 Release 2.9.0
• 0a86abd export some useful async thunk types
• d02c27a add docs for addAsyncThunk (#5066)
• ab346b9 fixdoc: incorrect position of keepUnusedDataFor for two scenarios (#5062)
• d2bbb8d Rewrite subscription handling and polling calculations for better perf (#5064)
• 3c6de47 Merge pull request #5065 from reduxjs/feature/TS5.9-matrix
• c37b977 Add missing error value
• 38537c3 Don't run Node10 checks for TS 6+
• 821be20 Add TS 5.9 to the matrix
• 407688d Abort pending requests if the cache entry is removed (#5061)
• Additional commits viewable in compare view

Sourced from @​typescript-eslint/eslint-plugin's releases.

v8.42.0

8.42.0 (2025-09-02)

🚀 Features

• deprecate tseslint.config() (#11531)

🩹 Fixes

• deps: update eslint monorepo to v9.33.0 (#11482)
• typescript-eslint: handle non-normalized windows paths produced by jiti (#11546)

❤️ Thank You

• Kirk Waiblinger @​kirkwaiblinger

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

Sourced from @​typescript-eslint/eslint-plugin's changelog.

8.42.0 (2025-09-02)

🩹 Fixes

• deps: update eslint monorepo to v9.33.0 (#11482)

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

• d135909 chore(release): publish 8.42.0
• 0daf303 chore: use new ESLint rules internally (#11558)
• ee3efa7 feat(typescript-estree): forbid invalid keys in EnumMember (#11497)
• 264ca2f fix(deps): update eslint monorepo to v9.33.0 (#11482)
• See full diff in compare view

This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for @​typescript-eslint/eslint-plugin since your current version.

Sourced from @​typescript-eslint/parser's releases.

v8.42.0

8.42.0 (2025-09-02)

🚀 Features

• deprecate tseslint.config() (#11531)

🩹 Fixes

• deps: update eslint monorepo to v9.33.0 (#11482)
• typescript-eslint: handle non-normalized windows paths produced by jiti (#11546)

❤️ Thank You

• Kirk Waiblinger @​kirkwaiblinger

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

Sourced from @​typescript-eslint/parser's changelog.

8.42.0 (2025-09-02)

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.

• d135909 chore(release): publish 8.42.0
• See full diff in compare view

This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for @​typescript-eslint/parser since your current version.

Sourced from jest's releases.

30.1.3

Fixes

• Fix unstable_mockModule with node: prefixed core modules.

Sourced from jest's changelog.

30.1.3

Fixes

• Fix unstable_mockModule with node: prefixed core modules.

• da9b532 v30.1.3
• See full diff in compare view

Sourced from sass's releases.

Dart Sass 1.92.0

To install Sass 1.92.0, download one of the packages below and add it to your PATH, or see the Sass website for full installation instructions.

Changes

• Breaking change: Emit declarations, childless at-rules, and comments in the order they appear in the source even when they're interleaved with nested rules. This obsoletes the mixed-decls deprecation.

• Breaking change: The function name type() is now fully reserved for the plain CSS function. This means that @function definitions with the name type will produce errors, while function calls will be parsed as special function strings.

• Configuring private variables using @use ... with, @forward ... with, and meta.load-css(..., $with: ...) is now deprecated. Private variables were always intended to be fully encapsulated within the module that defines them, and this helps enforce that encapsulation.

• Fix a bug where @extend rules loaded through a mixture of @import and @use rules could fail to apply correctly.

Command-Line Interface

• In --watch mode, delete the source map when the associated source file is deleted.

See the full changelog for changes in earlier releases.

Sourced from sass's changelog.

1.92.0

• Breaking change: Emit declarations, childless at-rules, and comments in the order they appear in the source even when they're interleaved with nested rules. This obsoletes the mixed-decls deprecation.

• Breaking change: The function name type() is now fully reserved for the plain CSS function. This means that @function definitions with the name type will produce errors, while function calls will be parsed as special function strings.

• Configuring private variables using @use ... with, @forward ... with, and meta.load-css(..., $with: ...) is now deprecated. Private variables were always intended to be fully encapsulated within the module that defines them, and this helps enforce that encapsulation.

• Fix a bug where @extend rules loaded through a mixture of @import and @use rules could fail to apply correctly.

Command-Line Interface

• In --watch mode, delete the source map when the associated source file is deleted.

• 055ef24 [Private Config] Implement the deprecation (#2631)
• 3526d62 Bump actions/attest-build-provenance from 2 to 3 (#2633)
• 87e2e1c Add support for the plain CSS type() function (#2630)
• 9009a64 Implement the new mixed declaration/comment/at-rule behavior (#2629)
• 6d3d928 Delete source maps when source files are deleted in watch mode (#2626)
• c61b098 Fix @extend through mixed @import and @use (#2627)
• dc923ed Update Jest snapshot URLs (#2628)
• See full diff in compare view

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions