chore(deps): update all dependencies #1895

renovate · 2025-03-20T22:19:56Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@eslint/compat	`1.2.6` -> `1.2.7`
@eslint/eslintrc	`3.2.0` -> `3.3.1`
@eslint/js (source)	`9.20.0` -> `9.23.0`
@reduxjs/toolkit (source)	`2.5.1` -> `2.6.1`
@sentry/browser (source)	`9.1.0` -> `9.8.0`
@sentry/core (source)	`9.1.0` -> `9.8.0`
@tanstack/react-query (source)	`5.66.0` -> `5.69.0`
@types/node (source)	`20.10.0` -> `20.17.25`
@types/react (source)	`19.0.8` -> `19.0.12`
@types/react-dom (source)	`19.0.3` -> `19.0.4`
@typescript-eslint/eslint-plugin (source)	`8.24.0` -> `8.27.0`
@typescript-eslint/parser (source)	`8.24.0` -> `8.27.0`
@vitejs/plugin-react-swc	`3.8.0` -> `3.8.1`
@vitest/coverage-v8 (source)	`3.0.5` -> `3.0.9`
eslint (source)	`9.20.1` -> `9.23.0`
eslint-config-prettier	`10.0.1` -> `10.1.1`
eslint-plugin-react-hooks (source)	`5.1.0` -> `5.2.0`
happy-dom	`17.1.0` -> `17.4.4`
postcss (source)	`8.5.2` -> `8.5.3`
prettier (source)	`3.5.1` -> `3.5.3`
react-hot-toast	`2.5.1` -> `2.5.2`
react-json-tree (source)	`0.19.0` -> `0.20.0`
react-router (source)	`7.1.5` -> `7.4.0`
sass-embedded	`1.85.0` -> `1.86.0`
stylelint (source)	`16.14.1` -> `16.16.0`
typescript (source)	`5.7.3` -> `5.8.2`
vite (source)	`6.1.0` -> `6.2.2`
vitest (source)	`3.0.5` -> `3.0.9`
vitest-fetch-mock	`0.4.3` -> `0.4.5`
yarn (source)	`4.6.0` -> `4.7.0`

Release Notes

eslint/rewrite (@eslint/compat)

`v1.2.7`

Compare Source

eslint/eslintrc (@eslint/eslintrc)

`v3.3.1`

Compare Source

Bug Fixes

correct types field in package.json (#184) (2f4cf3f)

`v3.3.0`

Compare Source

Features

Add types to package (#179) (cb546be)

eslint/eslint (@eslint/js)

Features

418717f feat: introduce new deprecated types for rules (#19238) (fnx)
5c5b802 feat: Add --ext CLI option (#19405) (Milos Djermanovic)

Bug Fixes

db5340d fix: update missing plugin message template (#19445) (Milos Djermanovic)
d8ffdd4 fix: do not exit process on rule crash (#19436) (Francesco Trotta)

Documentation

c5561ea docs: Update README (GitHub Actions Bot)
80b0485 docs: replace var with let and const in rule example (#19434) (Tanuj Kanti)
f67d5e8 docs: Update README (GitHub Actions Bot)
75afc61 docs: Update README (GitHub Actions Bot)
0636cab docs: Update Eleventy from v2 to v3 (#19415) (Amaresh S M)
dd7d930 docs: Update README (GitHub Actions Bot)

Chores

a8c9a9f chore: update @eslint/eslintrc and @eslint/js (#19453) (Francesco Trotta)
265e0cf chore: package.json update for @eslint/js release (Jenkins)
3401b85 test: add test for Rule.ReportDescriptor type (#19449) (Francesco Trotta)
e497aa7 chore: update rewrite dependencies (#19448) (Francesco Trotta)
dab5478 chore: better error message for missing plugin in config (#19402) (Tanuj Kanti)
ebfe2eb chore: set js language for bug report issue config block (#19439) (Josh Goldberg ✨)
5fd211d test: processors can return subpaths (#19425) (Milos Djermanovic)

reduxjs/redux-toolkit (@reduxjs/toolkit)

`v2.6.1`

Compare Source

This bugfix release fixes several assorted types issues with the initial infinite query feature release, and adds support for an optional signal argument to createAsyncThunk.

Changelog

Infinite Query Fixes

We've fixed several types issues that were reported with infinite queries after the 2.6.0 release:

matchFulfilled and providesTags now get the correct response types
We've added pre-typed Type* types to represent infinite queries, similar to the existing pre-defined types for queries and mutations
selectCachedArgsForQuery now supports fetching args for infinite query endpoints
We fixed some TS type portability issues with infinite queries that caused errors when generating TS declarations
useInfiniteQueryState/Subscription now correctly expect just the query arg, not the combined {queryArg, pageParam} object

Other Improvements

createAsyncThunk now accepts an optional {signal} argument. If provided, the internal AbortSignal handling will tie into that signal.

upsertQueryEntries now correctly generates provided tags for upserted cache entries.

What's Changed

Fix assorted infinite query types by @markerikson in https://github.com/reduxjs/redux-toolkit/pull/4869
Add providesTags handling for upsertQueryEntries by @markerikson in https://github.com/reduxjs/redux-toolkit/pull/4872
add infinite query type support for selectCachedArgsForQuery by @alexmotoc in https://github.com/reduxjs/redux-toolkit/pull/4880
add more Typed wrappers and make sure they're all exported by @EskiMojo14 in https://github.com/reduxjs/redux-toolkit/pull/4866
Fix infinite query type portability issues by @markerikson in https://github.com/reduxjs/redux-toolkit/pull/4881
support passing an external abortsignal to createAsyncThunk by @EskiMojo14 in https://github.com/reduxjs/redux-toolkit/pull/4860

Full Changelog: reduxjs/redux-toolkit@v2.6.0...v2.6.1

`v2.6.0`

Compare Source

This feature release adds infinite query support to RTK Query.

Changelog

RTK Query Infinite Query support

Since we first released RTK Query in 2021, we've had users asking us to add support for "infinite queries" - the ability to keep fetching additional pages of data for a given endpoint. It's been by far our most requested feature. Until recently, our answer was that we felt there were too many use cases to support with a single API design approach.

Last year, we revisited this concept and concluded that the best approach was to mimic the flexible infinite query API design from React Query. We had additional discussions with @tkdodo , who described the rationale and implementation approach and encouraged us to use their API design, and @riqts provided an initial implementation on top of RTKQ's existing internals.

We're excited to announce that this release officially adds full infinite query endpoint support to RTK Query!

Using Infinite Queries

As with React Query, the API design is based around "page param" values that act as the query arguments for fetching a specific page for the given cache entry.

Infinite queries are defined with a new build.infiniteQuery() endpoint type. It accepts all of the same options as normal query endpoints, but also needs an additional infiniteQueryOptions field that specifies the infinite query behaviors. With TypeScript, you must supply 3 generic arguments: build.infiniteQuery<ResultType, QueryArg, PageParam>, where ResultType is the contents of a single page, QueryArg is the type passed in as the cache key, and PageParam is the value used to request a specific page.

The endpoint must define an initialPageParam value that will be used as the default (and can be overridden if desired). It also needs a getNextPageParam callback that will calculate the params for each page based on the existing values, and optionally a getPreviousPageParam callback if reverse fetching is needed. Finally, a maxPages option can be provided to limit the entry cache size.

The query and queryFn methods now receive a {queryArg, pageParam} object, instead of just the queryArg.

For the cache entries and hooks, the data field is now an object like {pages: ResultType[], pageParams: PageParam[]>. This gives you flexibility in how you use the data for rendering.

const pokemonApi = createApi({
  baseQuery: fetchBaseQuery({ baseUrl: 'https://example.com/pokemon' }),
  endpoints: (build) => ({
    // 3 TS generics: page contents, query arg, page param
    getInfinitePokemonWithMax: build.infiniteQuery<Pokemon[], string, number>({
      infiniteQueryOptions: {
        // Must provide a default initial page param value
        initialPageParam: 1,
        // Optionally limit the number of cached pages
        maxPages: 3,
        // Must provide a `getNextPageParam` function
        getNextPageParam: (lastPage, allPages, lastPageParam, allPageParams) =>
          lastPageParam + 1,
        // Optionally provide a `getPreviousPageParam` function
        getPreviousPageParam: (
          firstPage,
          allPages,
          firstPageParam,
          allPageParams,
        ) => {
          return firstPageParam > 0 ? firstPageParam - 1 : undefined
        },
      },
      // The `query` function receives `{queryArg, pageParam}` as its argument
      query({ queryArg, pageParam }) {
        return `/type/${queryArg}?page=${pageParam}`
      },
    }),
  }),
})

As with all RTKQ functionality, the core logic is UI-agnostic and does not require React. However, using the RTKQ React entry point will also auto-generate useInfiniteQuery hooks for these endpoints. Infinite query hooks fetch the initial page, then provide fetchNext/PreviousPage functions to let you trigger requests for more pages.

function PokemonList({
    pokemonType = 'fire',
  }: {
    pokemonType?: string
   ) {
  const {
    data,
    isFetching,
    isSuccess,
    fetchNextPage,
    fetchPreviousPage,
    refetch,
  } = api.useGetInfinitePokemonInfiniteQuery(pokemonType)

  const handlePreviousPage = async () => {
    const res = await fetchPreviousPage()
  }

  const handleNextPage = async () => {
    const res = await fetchNextPage()
  }
  
  // `data` is a `{pages, pageParams}` object.
  // You can use those to render whatever UI you need.
  // In this case, flatten per-page arrays of results for this endpoint
  // into a single array to render a list.
  const allPokemon = data?.pages.flat() ?? [];

  // render UI with pages, show loading state, fetch as needed
}

Docs and Examples

The RTK Query docs have been updated with new content and explanations for infinite queries:

Usage Guides: Infinite Queries covers the new concepts, explains how to define infinite query endpoints and use the hooks, documents fetching behaviors, and describes common API interaction patterns
API Reference: createApi documents the new infinite query endpoint options
Generated API Slices: React Hooks has been updated to better organize the hook descriptions, and covers the infinite query hook arguments and behaviors

We've also added a new infinite query example app in the repo that shows several usage patterns like pagination, cursors, infinite scrolling, and limit+offset queries.

Notes

As with all new features and functionality, more code does mean an increase in bundle size.

We did extensive work to byte-shave and optimize the final bundle size for this feature. Final estimates indicate that this adds about 4.2Kmin to production bundles. That's comparable to React Query's infinite query support size.

However, given RTKQ's current architecture, that bundle size increase is included even if you aren't using any infinite query endpoints in your application. Given the significant additional functionality, that seems like an acceptable tradeoff. (And as always, having this kind of functionality built into RTKQ means that your app benefits when it uses this feature without having to add a lot of additional code to your own app, which would likely be much larger.)

Longer-term, we hope to investigate reworking some of RTKQ's internal architecture to potentially make some of the features opt-in for better bundle size optimizations, but don't have a timeline for that work.

Thanks

This new feature wouldn't have been possible without huge amounts of assistance from several people. We'd like to thank:

@tkdodo of TanStack Query, for happily letting us reuse the API design and implementation approach that they worked hard to figure out, and offering us his advice and knowledge on why they made specific design choices
@riqts , for building the first initial POC draft PR long before we were even ready to begin thinking about this ourselves
@remus-selea and @agusterodin , for trying out various stages of the draft PRs and offering significant detailed feedback and bug reports as I iterated on the implementation

What's Changed

[API Concept] - Infinite Query API by @riqts in https://github.com/reduxjs/redux-toolkit/pull/4393
RTKQ Infinite Query integration by @markerikson in https://github.com/reduxjs/redux-toolkit/pull/4738

and numerous specific sub-PRs that went into that integration PR as I worked through the implementation over the last few months.

Full Changelog: reduxjs/redux-toolkit@v2.5.1...v2.6.0

getsentry/sentry-javascript (@sentry/browser)

`v9.8.0`

Compare Source

feat(node): Implement new continuous profiling API spec (#15635)
feat(profiling): Add platform to chunk envelope (#15758)
feat(react): Export captureReactException method (#15746)
fix(node): Check for res.end before passing to Proxy (#15776)
perf(core): Add short-circuits to eventFilters integration (#15752)
perf(node): Short circuit flushing on Vercel only for Vercel (#15734)

Bundle size 📦

Path	Size
@sentry/browser	23.29 KB
@sentry/browser - with treeshaking flags	23.11 KB
@sentry/browser (incl. Tracing)	36.34 KB
@sentry/browser (incl. Tracing, Replay)	73.51 KB
@sentry/browser (incl. Tracing, Replay) - with treeshaking flags	66.94 KB
@sentry/browser (incl. Tracing, Replay with Canvas)	78.15 KB
@sentry/browser (incl. Tracing, Replay, Feedback)	90.71 KB
@sentry/browser (incl. Feedback)	40.43 KB
@sentry/browser (incl. sendFeedback)	27.94 KB
@sentry/browser (incl. FeedbackAsync)	32.73 KB
@sentry/react	25.1 KB
@sentry/react (incl. Tracing)	38.26 KB
@sentry/vue	27.53 KB
@sentry/vue (incl. Tracing)	38.04 KB
@sentry/svelte	23.33 KB
CDN Bundle	24.52 KB
CDN Bundle (incl. Tracing)	36.38 KB
CDN Bundle (incl. Tracing, Replay)	71.41 KB
CDN Bundle (incl. Tracing, Replay, Feedback)	76.61 KB
CDN Bundle - uncompressed	71.68 KB
CDN Bundle (incl. Tracing) - uncompressed	108.06 KB
CDN Bundle (incl. Tracing, Replay) - uncompressed	219.32 KB
CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed	231.88 KB
@sentry/nextjs (client)	39.56 KB
@sentry/sveltekit (client)	36.76 KB
@sentry/node	142.65 KB
@sentry/node - without tracing	96.04 KB
@sentry/aws-serverless	120.41 KB

`v9.7.0`

Compare Source

feat(core): Add captureLog method (#15717)
feat(remix/cloudflare): Export sentryHandleError (#15726)
fix(node): Always flush on Vercel before Lambda freeze (#15602)
fix(node): Ensure incoming traces are propagated without HttpInstrumentation (#15732)
fix(node): Use fatal level for unhandled rejections in strict mode (#15720)
fix(nuxt): Delete Nuxt server template injection (#15749)

Bundle size 📦

Path	Size
@sentry/browser	23.28 KB
@sentry/browser - with treeshaking flags	23.09 KB
@sentry/browser (incl. Tracing)	36.33 KB
@sentry/browser (incl. Tracing, Replay)	73.5 KB
@sentry/browser (incl. Tracing, Replay) - with treeshaking flags	66.93 KB
@sentry/browser (incl. Tracing, Replay with Canvas)	78.13 KB
@sentry/browser (incl. Tracing, Replay, Feedback)	90.69 KB
@sentry/browser (incl. Feedback)	40.42 KB
@sentry/browser (incl. sendFeedback)	27.91 KB
@sentry/browser (incl. FeedbackAsync)	32.7 KB
@sentry/react	25.08 KB
@sentry/react (incl. Tracing)	38.23 KB
@sentry/vue	27.52 KB
@sentry/vue (incl. Tracing)	38.02 KB
@sentry/svelte	23.3 KB
CDN Bundle	24.49 KB
CDN Bundle (incl. Tracing)	36.37 KB
CDN Bundle (incl. Tracing, Replay)	71.39 KB
CDN Bundle (incl. Tracing, Replay, Feedback)	76.57 KB
CDN Bundle - uncompressed	71.56 KB
CDN Bundle (incl. Tracing) - uncompressed	107.94 KB
CDN Bundle (incl. Tracing, Replay) - uncompressed	219.2 KB
CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed	231.77 KB
@sentry/nextjs (client)	39.52 KB
@sentry/sveltekit (client)	36.73 KB
@sentry/node	142.62 KB
@sentry/node - without tracing	96.01 KB
@sentry/aws-serverless	120.37 KB

`v9.6.1`

Compare Source

feat(deps): bump @prisma/instrumentation from 6.4.1 to 6.5.0 (#15714)
feat(deps): bump @sentry/cli from 2.42.2 to 2.42.3 (#15711)
fix(nextjs): Re-patch router if it is overridden by Next.js (#15721)
fix(nuxt): Add Nitro Rollup plugin to inject Sentry server config (#15710)
chore(deps): Bump rollup to 4.35.0 (#15651)

Bundle size 📦

Path	Size
@sentry/browser	23.15 KB
@sentry/browser - with treeshaking flags	22.94 KB
@sentry/browser (incl. Tracing)	36.21 KB
@sentry/browser (incl. Tracing, Replay)	73.39 KB
@sentry/browser (incl. Tracing, Replay) - with treeshaking flags	66.81 KB
@sentry/browser (incl. Tracing, Replay with Canvas)	78.01 KB
@sentry/browser (incl. Tracing, Replay, Feedback)	90.57 KB
@sentry/browser (incl. Feedback)	40.3 KB
@sentry/browser (incl. sendFeedback)	27.79 KB
@sentry/browser (incl. FeedbackAsync)	32.58 KB
@sentry/react	24.97 KB
@sentry/react (incl. Tracing)	38.1 KB
@sentry/vue	27.4 KB
@sentry/vue (incl. Tracing)	37.9 KB
@sentry/svelte	23.18 KB
CDN Bundle	24.36 KB
CDN Bundle (incl. Tracing)	36.26 KB
CDN Bundle (incl. Tracing, Replay)	71.27 KB
CDN Bundle (incl. Tracing, Replay, Feedback)	76.45 KB
CDN Bundle - uncompressed	71.19 KB
CDN Bundle (incl. Tracing) - uncompressed	107.57 KB
CDN Bundle (incl. Tracing, Replay) - uncompressed	218.83 KB
CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed	231.39 KB
@sentry/nextjs (client)	39.38 KB
@sentry/sveltekit (client)	36.63 KB
@sentry/node	142.29 KB
@sentry/node - without tracing	95.71 KB
@sentry/aws-serverless	120.06 KB

`v9.6.0`

Compare Source

Important Changes

feat(tanstackstart): Add @sentry/tanstackstart-react package and make @sentry/tanstackstart package a utility package (#15629)

Since TanStack Start is supposed to be a generic framework that supports libraries like React and Solid, the @sentry/tanstackstart SDK package was renamed to @sentry/tanstackstart-react to reflect that the SDK is specifically intended to be used for React TanStack Start applications.
Note that the TanStack Start SDK is still in alpha status and may be subject to breaking changes in non-major package updates.

Other Changes

feat(astro): Accept all vite-plugin options (#15638)
feat(deps): bump @sentry/webpack-plugin from 3.2.1 to 3.2.2 (#15627)
feat(tanstackstart): Refine initial API (#15574)
fix(core): Ensure fill only patches functions (#15632)
fix(nextjs): Consider pageExtensions when looking for instrumentation file (#15701)
fix(remix): Null-check options (#15610)
fix(sveltekit): Correctly parse angle bracket type assertions for auto instrumentation (#15578)
fix(sveltekit): Guard process variable (#15605)

Work in this release was contributed by @angelikatyborska and @nwalters512. Thank you for your contributions!

Bundle size 📦

Path	Size
@sentry/browser	23.15 KB
[@&#8

Configuration

📅 Schedule: Branch creation - "on the first day of january" (UTC), 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.

webteam-app · 2025-03-20T22:20:00Z

renovate bot force-pushed the renovate/all branch from 9067463 to 2e3e4ec Compare March 21, 2025 20:57

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

chore(deps): update all dependencies #1895

chore(deps): update all dependencies #1895

renovate bot commented Mar 20, 2025 •

edited

Loading

webteam-app commented Mar 20, 2025

chore(deps): update all dependencies #1895

Are you sure you want to change the base?

chore(deps): update all dependencies #1895

Conversation

renovate bot commented Mar 20, 2025 • edited Loading

Release Notes

Bug Fixes

Features

Features

Bug Fixes

Documentation

Chores

Changelog

Infinite Query Fixes

Other Improvements

What's Changed

Changelog

RTK Query Infinite Query support

Using Infinite Queries

Docs and Examples

Notes

Thanks

What's Changed

Bundle size 📦

Bundle size 📦

Bundle size 📦

Important Changes

Other Changes

Bundle size 📦

Configuration

webteam-app commented Mar 20, 2025

renovate bot commented Mar 20, 2025 •

edited

Loading