fix(deps): update all non-major dependencies #1833
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^8.0.0-alpha.15
->^8.0.0-alpha.16
^7.26.8
->^7.26.9
^7.26.8
->^7.26.9
^7.26.8
->^7.26.9
^7.26.7
->^7.26.9
^2.10.5
->^2.10.6
^2.27.12
->^2.28.1
^3.2.4
->^3.2.5
^1.2.6
->^1.2.7
^9.20.0
->^9.21.0
^2.5.1
->^2.6.0
^8.5.3
->^8.6.2
^8.5.3
->^8.6.2
^8.5.3
->^8.6.2
^8.5.3
->^8.6.2
2.0.0
->2.1.0
^8.5.3
->^8.6.2
^8.5.3
->^8.6.2
^8.5.3
->^8.6.2
^8.5.3
->^8.6.2
^0.0.304
->^0.0.306
^22.13.1
->^22.13.5
^8.24.0
->^8.25.0
^8.24.0
->^8.25.0
^2.3.0
->^2.3.2
^9.20.0
->^9.21.0
^10.0.1
->^10.0.2
^15.14.0
->^15.15.0
^5.0.9
->^5.1.2
9.15.5
->9.15.6
3.5.0
->3.5.2
^5.4.0
->^5.5.0
^6.29.0
->^6.30.0
^7.8.1
->^7.8.2
^4.28.1
->^4.29.0
^8.5.3
->^8.6.2
^29.2.5
->^29.2.6
^8.24.0
->^8.25.0
^5.97.1
->^5.98.0
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
.d.ts
for TypeScript <= 4.0 (@nicolo-ribaudo)babel-generator
,babel-parser
,babel-plugin-transform-template-literals
,babel-traverse
,babel-types
babel-generator
,babel-parser
,babel-plugin-transform-typescript
,babel-types
export import =
as an ExportNamedDeclaration (@JLHwung)babel-preset-env
babel-parser
babel-parser
,babel-plugin-transform-typescript
,babel-types
typeof this
(@JLHwung)🐛 Bug Fix
babel-generator
babel-parser
🏠 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
babel-types
TSPropertySignature.kind
(@liuxingbaoyu)babel-generator
,babel-types
🏠 Internal
babel-types
.ts
files with explicit reexports to solve name conflicts (@nicolo-ribaudo)babel-core
@types/gensync
in Babel 7 (@nicolo-ribaudo)changesets/changesets (@changesets/cli)
v2.28.1
Compare Source
Patch Changes
b9df596
]:v2.28.0
Compare Source
Minor Changes
84a4a1b
Thanks @bennypowers! - Added a new config option to opt-out from formatting with Prettier usingprettier: false
.Patch Changes
84a4a1b
,84a4a1b
]: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
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: replacevar
withlet
andconst
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 forRule.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 additionalinfiniteQueryOptions
field that specifies the infinite query behaviors. With TypeScript, you must supply 3 generic arguments:build.infiniteQuery<ResultType, QueryArg, PageParam>
, whereResultType
is the contents of a single page,QueryArg
is the type passed in as the cache key, andPageParam
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 agetNextPageParam
callback that will calculate the params for each page based on the existing values, and optionally agetPreviousPageParam
callback if reverse fetching is needed. Finally, amaxPages
option can be provided to limit the entry cache size.The
query
andqueryFn
methods now receive a{queryArg, pageParam}
object, instead of just thequeryArg
.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.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 providefetchNext/PreviousPage
functions to let you trigger requests for more pages.Docs and Examples
The RTK Query docs have been updated with new content and explanations for infinite queries:
createApi
documents the new infinite query endpoint optionsWe'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:
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:
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.
This PR was generated by Mend Renovate. View the repository job log.