Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(deps): update all non-major dependencies #1833

Merged
merged 1 commit into from
Feb 27, 2025

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 17, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@babel/code-frame (source) ^8.0.0-alpha.15 -> ^8.0.0-alpha.16 age adoption passing confidence
@babel/core (source) ^7.26.8 -> ^7.26.9 age adoption passing confidence
@babel/plugin-transform-runtime (source) ^7.26.8 -> ^7.26.9 age adoption passing confidence
@babel/preset-env (source) ^7.26.8 -> ^7.26.9 age adoption passing confidence
@babel/runtime (source) ^7.26.7 -> ^7.26.9 age adoption passing confidence
@chakra-ui/react (source) ^2.10.5 -> ^2.10.6 age adoption passing confidence
@changesets/cli (source) ^2.27.12 -> ^2.28.1 age adoption passing confidence
@chromatic-com/storybook ^3.2.4 -> ^3.2.5 age adoption passing confidence
@eslint/compat ^1.2.6 -> ^1.2.7 age adoption passing confidence
@eslint/js (source) ^9.20.0 -> ^9.21.0 age adoption passing confidence
@reduxjs/toolkit (source) ^2.5.1 -> ^2.6.0 age adoption passing confidence
@storybook/addon-essentials (source) ^8.5.3 -> ^8.6.2 age adoption passing confidence
@storybook/addon-interactions (source) ^8.5.3 -> ^8.6.2 age adoption passing confidence
@storybook/addon-links (source) ^8.5.3 -> ^8.6.2 age adoption passing confidence
@storybook/addon-onboarding (source) ^8.5.3 -> ^8.6.2 age adoption passing confidence
@storybook/addon-webpack5-compiler-swc 2.0.0 -> 2.1.0 age adoption passing confidence
@storybook/blocks (source) ^8.5.3 -> ^8.6.2 age adoption passing confidence
@storybook/react (source) ^8.5.3 -> ^8.6.2 age adoption passing confidence
@storybook/react-webpack5 (source) ^8.5.3 -> ^8.6.2 age adoption passing confidence
@storybook/test (source) ^8.5.3 -> ^8.6.2 age adoption passing confidence
@types/chrome (source) ^0.0.304 -> ^0.0.306 age adoption passing confidence
@types/node (source) ^22.13.1 -> ^22.13.5 age adoption passing confidence
@typescript-eslint/eslint-plugin (source) ^8.24.0 -> ^8.25.0 age adoption passing confidence
@typescript-eslint/parser (source) ^8.24.0 -> ^8.25.0 age adoption passing confidence
anser ^2.3.0 -> ^2.3.2 age adoption passing confidence
eslint (source) ^9.20.0 -> ^9.21.0 age adoption passing confidence
eslint-config-prettier ^10.0.1 -> ^10.0.2 age adoption passing confidence
globals ^15.14.0 -> ^15.15.0 age adoption passing confidence
nanoid ^5.0.9 -> ^5.1.2 age adoption passing confidence
pnpm (source) 9.15.5 -> 9.15.6 age adoption passing confidence
prettier (source) 3.5.0 -> 3.5.2 age adoption passing confidence
react-icons ^5.4.0 -> ^5.5.0 age adoption passing confidence
react-router-dom (source) ^6.29.0 -> ^6.30.0 age adoption passing confidence
rxjs (source) ^7.8.1 -> ^7.8.2 age adoption passing confidence
selenium-webdriver (source) ^4.28.1 -> ^4.29.0 age adoption passing confidence
storybook (source) ^8.5.3 -> ^8.6.2 age adoption passing confidence
ts-jest (source) ^29.2.5 -> ^29.2.6 age adoption passing confidence
typescript-eslint (source) ^8.24.0 -> ^8.25.0 age adoption passing confidence
webpack ^5.97.1 -> ^5.98.0 age adoption passing confidence

Release Notes

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

v8.0.0-alpha.16

Compare Source

v8.0.0-alpha.16 (2025-02-14)

In addition to the changelog below, this release includes changes from v7.26.6 to v7.26.9.

💥 Breaking Change
  • babel-types
  • babel-generator, babel-parser, babel-plugin-transform-template-literals, babel-traverse, babel-types
  • babel-generator, babel-parser, babel-plugin-transform-typescript, babel-types
  • babel-preset-env
  • babel-parser
  • babel-parser, babel-plugin-transform-typescript, babel-types
🐛 Bug Fix
🏠 Internal
  • babel-parser, babel-plugin-proposal-pipeline-operator, babel-plugin-syntax-pipeline-operator
Committers: 7
babel/babel (@​babel/core)

v7.26.9

Compare Source

🐛 Bug Fix
🏠 Internal
changesets/changesets (@​changesets/cli)

v2.28.1

Compare Source

Patch Changes

v2.28.0

Compare Source

Minor Changes
Patch Changes
chromaui/addon-visual-tests (@​chromatic-com/storybook)

v3.2.5

Compare Source

eslint/rewrite (@​eslint/compat)

v1.2.7

Compare Source

eslint/eslint (@​eslint/js)

v9.21.0

Compare Source

Features
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.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:

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

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

storybookjs/storybook (@​storybook/addon-essentials)

v8.6.2

Compare Source

v8.6.1

Compare Source

v8.6.0

Compare Source

The 8.6 release focuses on Storybook Test, which brings realtime component, accessibility, and visual UI tests to your favorite component workshop.

Here’s what’s new:

  • 🎁 Storybook Test installer for out-of-the-box tests in new projects
  • 🦾 Accessibility “todo” workflow to systematically fix a11y violations
  • 🗜️ 80% smaller create-storybook package for much faster installs
  • 🧪 Dozens of Test fixes based on user feedback
  • 📕 Docs fixes for table of contents, code snippets, and more
  • 🚨 Key security fixes for Vite and ESbuild
  • 💯 Hundreds more improvements
List of all updates

Configuration

📅 Schedule: 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.

Copy link

changeset-bot bot commented Feb 17, 2025

⚠️ No Changeset found

Latest commit: 85e9619

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

@renovate renovate bot force-pushed the renovate/all-minor-patch branch 16 times, most recently from 64a956c to 1972205 Compare February 25, 2025 11:17
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from aa23045 to 43f0444 Compare February 27, 2025 14:51
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 43f0444 to 85e9619 Compare February 27, 2025 18:48
@Methuselah96 Methuselah96 merged commit e46bbca into main Feb 27, 2025
1 check passed
@Methuselah96 Methuselah96 deleted the renovate/all-minor-patch branch February 27, 2025 21:40
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.

1 participant