chore(deps): update all non-major dependencies #9784
Conversation
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=80&v=4){kind=small}
|
github-actions
bot
added
package: react-query-devtools
package: react-query
package: react-query-persist-client
package: vue-query
package: query-core
package: solid-query
package: query-persist-client-core
package: eslint-plugin-query
package: svelte-query
package: svelte-query-devtools
package: query-devtools
package: angular-query-experimental
package: query-async-storage-persister
package: query-sync-storage-persister
package: solid-query-persist-client
package: svelte-query-persist-client
package: vue-query-devtools
package: solid-query-devtools
package: query-broadcast-client-experimental
package: react-query-next-experimental
package: angular-query-persist-client
package: query-test-utils
labels
WalkthroughThis PR updates dependency and devDependency versions across many example projects, integrations, packages, and root tooling (Angular, Vite, Svelte, Solid, React, Vue, testing and lint tooling). No source code or runtime logic changes were made; edits are limited to package.json version bumps. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Suggested reviewers
Poem
Pre-merge checks and finishing touches❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✨ Finishing touches🧪 Generate unit tests (beta)
📜 Recent review detailsConfiguration used: CodeRabbit UI Review profile: CHILL Plan: Pro ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (79)
✅ Files skipped from review due to trivial changes (1)
🚧 Files skipped from review as they are similar to previous changes (42)
🧰 Additional context used🧠 Learnings (1)📚 Learning: 2025-09-02T17:57:33.184ZApplied to files:
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)
🔇 Additional comments (37)
Comment |
|
View your CI Pipeline Execution ↗ for commit 3b87487
☁️ Nx Cloud last updated this comment at |
|
Sizes for commit 3b87487:
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 2
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
⛔ Files ignored due to path filters (1)
pnpm-lock.yamlis excluded by!**/pnpm-lock.yaml
📒 Files selected for processing (79)
examples/angular/auto-refetching/package.json(1 hunks)examples/angular/basic-persister/package.json(1 hunks)examples/angular/basic/package.json(1 hunks)examples/angular/devtools-panel/package.json(1 hunks)examples/angular/infinite-query-with-max-pages/package.json(1 hunks)examples/angular/optimistic-updates/package.json(1 hunks)examples/angular/pagination/package.json(1 hunks)examples/angular/query-options-from-a-service/package.json(1 hunks)examples/angular/router/package.json(1 hunks)examples/angular/rxjs/package.json(1 hunks)examples/angular/simple/package.json(1 hunks)examples/react/algolia/package.json(2 hunks)examples/react/basic-graphql-request/package.json(1 hunks)examples/react/basic/package.json(1 hunks)examples/react/chat/package.json(1 hunks)examples/react/default-query-function/package.json(1 hunks)examples/react/devtools-panel/package.json(1 hunks)examples/react/eslint-legacy/package.json(1 hunks)examples/react/offline/package.json(1 hunks)examples/react/playground/package.json(1 hunks)examples/react/react-native/package.json(1 hunks)examples/react/react-router/package.json(1 hunks)examples/react/rick-morty/package.json(1 hunks)examples/react/shadow-dom/package.json(1 hunks)examples/react/simple/package.json(1 hunks)examples/react/star-wars/package.json(1 hunks)examples/react/suspense/package.json(1 hunks)examples/solid/astro/package.json(1 hunks)examples/solid/basic-graphql-request/package.json(1 hunks)examples/solid/basic/package.json(1 hunks)examples/solid/default-query-function/package.json(1 hunks)examples/solid/simple/package.json(1 hunks)examples/solid/solid-start-streaming/package.json(1 hunks)examples/svelte/auto-refetching/package.json(1 hunks)examples/svelte/basic/package.json(1 hunks)examples/svelte/load-more-infinite-scroll/package.json(1 hunks)examples/svelte/optimistic-updates/package.json(1 hunks)examples/svelte/playground/package.json(1 hunks)examples/svelte/simple/package.json(1 hunks)examples/svelte/ssr/package.json(1 hunks)examples/svelte/star-wars/package.json(1 hunks)examples/vue/2.6-basic/package.json(1 hunks)examples/vue/2.7-basic/package.json(1 hunks)examples/vue/basic/package.json(1 hunks)examples/vue/dependent-queries/package.json(1 hunks)examples/vue/nuxt3/package.json(1 hunks)examples/vue/persister/package.json(1 hunks)examples/vue/simple/package.json(1 hunks)integrations/angular-cli-20/package.json(1 hunks)integrations/react-next-15/package.json(1 hunks)integrations/react-vite/package.json(1 hunks)integrations/react-webpack-4/package.json(1 hunks)integrations/react-webpack-5/package.json(1 hunks)integrations/solid-vite/package.json(1 hunks)integrations/svelte-vite/package.json(1 hunks)integrations/vue-vite/package.json(1 hunks)package.json(3 hunks)packages/angular-query-experimental/package.json(1 hunks)packages/angular-query-persist-client/package.json(1 hunks)packages/eslint-plugin-query/package.json(1 hunks)packages/query-async-storage-persister/package.json(1 hunks)packages/query-broadcast-client-experimental/package.json(1 hunks)packages/query-core/package.json(1 hunks)packages/query-devtools/package.json(1 hunks)packages/query-persist-client-core/package.json(1 hunks)packages/query-sync-storage-persister/package.json(1 hunks)packages/query-test-utils/package.json(1 hunks)packages/react-query-devtools/package.json(1 hunks)packages/react-query-next-experimental/package.json(1 hunks)packages/react-query-persist-client/package.json(1 hunks)packages/react-query/package.json(1 hunks)packages/solid-query-devtools/package.json(1 hunks)packages/solid-query-persist-client/package.json(1 hunks)packages/solid-query/package.json(1 hunks)packages/svelte-query-devtools/package.json(1 hunks)packages/svelte-query-persist-client/package.json(1 hunks)packages/svelte-query/package.json(1 hunks)packages/vue-query-devtools/package.json(1 hunks)packages/vue-query/package.json(1 hunks)
🧰 Additional context used
🧠 Learnings (1)
📚 Learning: 2025-09-02T17:57:33.184Z
Learnt from: TkDodo
PR: TanStack/query#9612
File: packages/query-async-storage-persister/src/asyncThrottle.ts:0-0
Timestamp: 2025-09-02T17:57:33.184Z
Learning: When importing from tanstack/query-core in other TanStack Query packages like query-async-storage-persister, a workspace dependency "tanstack/query-core": "workspace:*" needs to be added to the package.json.
Applied to files:
packages/query-core/package.jsonpackages/query-broadcast-client-experimental/package.jsonintegrations/solid-vite/package.jsonexamples/solid/basic-graphql-request/package.jsonpackages/solid-query-persist-client/package.jsonintegrations/react-vite/package.jsonpackages/svelte-query-persist-client/package.jsonpackages/vue-query-devtools/package.jsonpackages/react-query-persist-client/package.jsonpackages/query-sync-storage-persister/package.jsonpackages/react-query-devtools/package.jsonpackages/query-persist-client-core/package.jsonpackages/svelte-query-devtools/package.jsonpackages/react-query-next-experimental/package.jsonpackages/svelte-query/package.jsonpackages/angular-query-experimental/package.jsonintegrations/react-next-15/package.jsonpackages/react-query/package.jsonpackages/query-async-storage-persister/package.jsonpackages/angular-query-persist-client/package.json
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)
- GitHub Check: Test
- GitHub Check: Preview
🔇 Additional comments (81)
packages/react-query-next-experimental/package.json (1)
61-61: Dependency updates look good.Minor version bumps for
@vitejs/plugin-react(4.3.4 → 4.7.0) and patch bump fornpm-run-all2(5.0.0 → 5.0.2) are standard, backward-compatible updates aligned with the PR's non-major dependency upgrade objective.Also applies to: 63-63
examples/vue/2.7-basic/package.json (1)
11-11: Patch version bump approved.The update to
@tanstack/vue-query(5.90.2 → 5.90.5) is a safe patch-level increment.packages/query-core/package.json (1)
63-63: Patch version bump approved.The update to
npm-run-all2(5.0.0 → 5.0.2) is a safe patch-level increment to a build-time tool.packages/vue-query/package.json (2)
66-66: Clarify the @vue/devtools-api change.Line 66 is marked as modified, but the summary does not specify the version change for
@vue/devtools-api. Confirm whether this is a version bump and, if so, verify compatibility with the Vue ecosystem versions in use.
73-73: Patch version bump approved.The update to
eslint-plugin-vue(10.5.0 → 10.5.1) is a safe patch-level increment.integrations/vue-vite/package.json (1)
13-13: Minor version bumps are generally safe; verify Vite tooling compatibility.Updates to
@vitejs/plugin-vue(5.2.1 → 5.2.4) andvite(6.3.6 → 6.4.0) are within major versions and should be backward compatible. However, ensure the minor version bump of Vite aligns with the plugin's expectations.Also applies to: 15-15
packages/query-persist-client-core/package.json (1)
66-66: Patch version bump approved.The update to
npm-run-all2(5.0.0 → 5.0.2) is a safe patch-level increment to a build-time tool.packages/query-async-storage-persister/package.json (1)
67-67: Patch version bump approved.The update to
npm-run-all2(5.0.0 → 5.0.2) is a safe patch-level increment to a build-time tool.packages/react-query-devtools/package.json (1)
86-86: Dependency updates look good.Minor version bumps for
@testing-library/react(16.1.0 → 16.3.0) and@vitejs/plugin-react(4.3.4 → 4.7.0), along with patch bump fornpm-run-all2(5.0.0 → 5.0.2), are all backward-compatible updates to development tooling aligned with the PR's non-major dependency upgrade objective.Also applies to: 88-88, 89-89
examples/vue/basic/package.json (1)
16-16: Dependency updates look appropriate.Minor/patch updates to Vite and its Vue plugin are well within the caret ranges and should be compatible.
Also applies to: 18-18
examples/vue/dependent-queries/package.json (1)
15-15: Consistent devDependency updates across Vue examples.Same Vite and plugin updates as other Vue examples—straightforward minor/patch bumps.
Also applies to: 17-17
integrations/svelte-vite/package.json (1)
12-13: Straightforward minor updates to Svelte and Vite.Both updates are patch/minor within the specified ranges and align with the broader dependency refresh across the project.
examples/vue/nuxt3/package.json (1)
10-10: Dependency updates are within safe ranges.The patch bump to @tanstack/vue-query and minor bump to Nuxt 3.19.3 are both within the specified caret ranges and should maintain compatibility.
Also applies to: 13-13
examples/svelte/basic/package.json (1)
17-18: Svelte ecosystem updates are compatible.Multiple minor/patch bumps to Svelte, SvelteKit, and Vite are all within their specified ranges. The update to SvelteKit 2.47.2 (from 2.42.2) represents multiple minor versions but stays within the ^2 constraint, maintaining compatibility.
Also applies to: 20-21, 23-23
packages/query-test-utils/package.json (1)
38-38: Safe patch update to npm-run-all2.Patch bump from 5.0.0 to 5.0.2 is low-risk for this internal test utility package.
examples/vue/2.6-basic/package.json (1)
11-11: Patch update to @tanstack/vue-query is safe.The bump from 5.90.2 to 5.90.5 is a standard patch release and maintains compatibility with the Vue 2.6 legacy example.
integrations/react-next-15/package.json (1)
9-9: Breaking changes in @js-temporal/polyfill 0.5.1 require verification against example code.Substantive breaking changes exist between 0.4.4 and 0.5.1, including parsing/validation changes where plain date-only strings behavior has changed. The React 19 example directly uses this pattern: Temporal.PlainDate.from('2024-01-01') and Temporal.PlainDate.from('2023-01-01') in page.tsx and client-component.tsx.
Verify that these calls still work with 0.5.1 or update the code accordingly. If you're unsure whether the parsing changes affect PlainDate specifically, test the example locally or consult the full v0.4.0→v0.5.0 migration notes.
examples/vue/simple/package.json (1)
15-19: LGTM!Standard maintenance updates for Vue tooling. Patch and minor updates are low-risk and align with the broader PR dependency refresh.
packages/vue-query-devtools/package.json (1)
55-63: LGTM!Patch and minor updates for Vue devtools dependencies are low-risk and correctly categorized in devDependencies.
examples/svelte/load-more-infinite-scroll/package.json (1)
14-22: LGTM!Svelte ecosystem updates (adapter, kit, svelte, svelte-check, vite) are all patch/minor updates, correctly placed in devDependencies. These align with the broader PR dependency refresh and pose minimal risk.
packages/solid-query-devtools/package.json (1)
68-75: LGTM!Patch updates for Solid ecosystem dependencies (npm-run-all2, solid-js, vite-plugin-solid) are low-risk and correctly placed in devDependencies. Versions are consistent with solid-query package updates.
examples/angular/basic-persister/package.json (1)
11-28: LGTM!Angular package updates from 20.0.0 to 20.3.6 are consistent across all @angular packages, with zone.js patched to 0.15.1 in alignment. These are safe minor-version updates within the 20.x series. Correctly categorized between dependencies and devDependencies.
packages/solid-query/package.json (1)
71-78: LGTM!Patch updates for Solid ecosystem dependencies are low-risk and correctly placed. Versions align with solid-query-devtools and other Solid packages in this PR.
examples/solid/solid-start-streaming/package.json (1)
14-14: Solid framework and tooling updates look good.Minor and patch version bumps for Solid.js ecosystem dependencies are compatible. Caret-ranged constraints allow flexibility as expected.
Also applies to: 17-18
examples/react/algolia/package.json (2)
11-11: Verify Algolia version specifier is intentional.The @algolia/client-search version was updated from 5.2.1 to 5.40.1 (exact specifier). This is a significant jump within the 5.x range. Confirm:
- Whether the exact version specification (no caret) is intentional and aligns with the package's lock file strategy
- Whether release notes for 5.2→5.40 contain any relevant breaking changes or migration notes
21-21: Vite and React tooling updates approved.Minor and patch bumps for @vitejs/plugin-react and vite are compatible and consistent with other React examples in the PR.
Also applies to: 23-23
examples/solid/astro/package.json (1)
15-15: Solid and Astro ecosystem updates approved.All dependency updates are minor/patch versions with appropriate caret constraints. No compatibility concerns anticipated.
Also applies to: 17-17, 21-22
examples/react/basic-graphql-request/package.json (1)
13-14: GraphQL and Vite tooling updates approved.All dependency updates are minor/patch versions. GraphQL, graphql-request, and Vite tools are all compatible with their caret constraints.
Also applies to: 19-20
packages/query-broadcast-client-experimental/package.json (1)
62-62: Dependency updates for published package approved with verification.All updates are minor/patch versions. Since
@tanstack/query-broadcast-client-experimentalis a published package, ensure the test suite passes with the updatedbroadcast-channeland@testing-library/reactversions to confirm compatibility.Also applies to: 65-67
examples/angular/optimistic-updates/package.json (1)
12-16: Angular framework and zone.js updates approved.All Angular packages updated to ^20.3.6 (within same major version) and zone.js patched to 0.15.1. These are standard maintenance updates with no breaking changes anticipated. Consistent with other Angular examples in the PR.
Also applies to: 20-20, 23-25
examples/solid/basic/package.json (1)
13-13: Solid and Vite tooling patch updates approved.All dependency updates are patch versions with caret constraints. No compatibility concerns.
Also applies to: 17-18
examples/svelte/ssr/package.json (1)
15-16: Svelte and SvelteKit ecosystem updates approved.All devDependency updates are minor/patch versions. @sveltejs/kit sees a moderate jump from 2.42.2 → 2.47.2 and svelte from 5.39.3 → 5.41.0, both within semver compatibility. Caret constraints provide appropriate flexibility. Recommend verifying the test suite runs successfully with these intermediate versions.
Also applies to: 18-19, 21-21
integrations/react-webpack-5/package.json (1)
14-18: Babel and webpack tooling updates look good.The updates to @babel/core, @babel/preset-env, @babel/preset-react, and html-webpack-plugin are all minor/patch version bumps within the same major versions. The caret ranges (^) allow compatible updates automatically, and babel-preset-react intentionally lags behind core/preset-env slightly, which is a normal pattern in Babel versioning.
packages/react-query-persist-client/package.json (1)
67-70: Testing library and build tool updates are safe.All three devDependency updates (@testing-library/react, @vitejs/plugin-react, npm-run-all2) are minor or patch version bumps. No breaking changes are anticipated in these ranges.
integrations/react-webpack-4/package.json (1)
14-17: Babel and babel-loader updates are compatible.The Babel package updates mirror those in react-webpack-5, and babel-loader 8.4.1 is fully compatible with @babel/core 7.28.4. This is a safe update for Webpack 4 projects.
examples/solid/default-query-function/package.json (1)
13-13: Solid example dependencies updated safely.All three dependency updates (solid-js, vite, vite-plugin-solid) are minor or patch bumps within the same major versions. Vite 6.4.0 is compatible with vite-plugin-solid 2.11.9.
Also applies to: 17-18
examples/solid/simple/package.json (1)
13-13: Solid example updates are consistent across the monorepo.The dependency updates in this file match the pattern seen in examples/solid/default-query-function/package.json, ensuring consistency across Solid examples.
Also applies to: 18-19
packages/svelte-query/package.json (1)
55-55: Svelte ecosystem packages updated consistently.All devDependency updates are minor or patch version bumps within the Svelte 5 ecosystem. @typescript-eslint/parser, eslint-plugin-svelte, svelte, and svelte-check are all being updated in alignment across related Svelte packages in this PR.
Also applies to: 59-62
examples/svelte/playground/package.json (1)
15-16: Svelte example tooling and framework updates are safe.All updates (@sveltejs/adapter-auto, @sveltejs/kit, svelte, svelte-check, vite) are minor or patch bumps. The SvelteKit minor bump (2.42.2 → 2.47.2) is a standard maintenance update within the same major version.
Also applies to: 18-19, 21-21
examples/solid/basic-graphql-request/package.json (1)
13-15: GraphQL and Solid example dependencies updated consistently.The graphql (16.9.0 → 16.11.0) and graphql-request (7.1.2 → 7.3.1) updates are minor/patch bumps. Solid and Vite updates align with the broader updates seen across other Solid examples in this PR.
Also applies to: 19-20
examples/svelte/optimistic-updates/package.json (1)
15-21: Dependency updates look good; recommend running tests to verify compatibility.All updates are non-breaking patch or minor versions within the caret ranges. However, since Vite and SvelteKit are relatively high-velocity projects, recommend running the example's
devandbuildscripts to confirm no subtle breaking changes.examples/svelte/auto-refetching/package.json (1)
15-21: Consistent Svelte tooling updates across examples.These updates match the concurrent updates in the other Svelte example packages and follow the same non-breaking patch/minor pattern.
examples/angular/simple/package.json (1)
12-24: Angular patch-level updates are consistent and appropriate.Updates to Angular 20.3.6 are all patch-level changes within the major version and are consistent across all Angular examples. Note:
zone.jsis correctly pinned to0.15.1(not using^), which is the correct approach for zone.js due to its strict versioning requirements.examples/svelte/star-wars/package.json (1)
15-23: Verify Tailwind updates—prior versions not shown in diff.The
@tailwindcss/viteandtailwindcssupdates to^4.1.14lack visible prior versions in the provided diff context. If this is a major version upgrade (e.g., v3→v4), confirm there are no breaking changes or required configuration updates for the example.examples/angular/pagination/package.json (1)
12-24: Angular updates are consistent with other Angular examples.Identical patch-level updates to Angular 20.3.6 and zone.js 0.15.1 as seen in other Angular example packages.
examples/angular/devtools-panel/package.json (1)
12-25: Angular updates are consistent, including @angular/router.Patch-level updates matching other Angular examples. The inclusion of
@angular/routeris expected for this example's routing needs.packages/eslint-plugin-query/package.json (1)
62-69: ESLint and TypeScript-ESLint updates are minor-level and appropriately coordinated.All
@typescript-eslint/*packages are updated together to^8.46.1, which maintains consistency. Theeslintandnpm-run-all2updates are also minor/patch level and should not introduce breaking changes. Consider runningnpm run test:libandnpm run test:eslintto verify no regressions.examples/angular/infinite-query-with-max-pages/package.json (1)
12-24: Angular updates are consistent with other Angular examples.Identical patch-level updates to Angular 20.3.6 and zone.js 0.15.1.
examples/angular/auto-refetching/package.json (1)
12-24: Version bumps are consistent and low-risk.Angular packages aligned to ^20.3.6 and zone.js pinned to 0.15.1 are all compatible patch/minor updates within the same major version range. All related framework packages and tooling are updated in tandem.
examples/svelte/simple/package.json (1)
16-20: Svelte and Vite tooling updates are appropriate.Minor/patch updates to Svelte (5.39.3 → 5.41.0), build tooling (@tsconfig/svelte, svelte-check), and Vite (6.3.6 → 6.4.0) are standard maintenance updates within semver compatibility ranges.
packages/query-devtools/package.json (1)
67-80: Solid.js ecosystem updates are cohesive.Patch and minor updates to Solid.js libraries (solid-js 1.9.7 → 1.9.9, vite-plugin-solid 2.11.6 → 2.11.9) and other devDependencies are consistent and low-risk. Workspace dependencies remain intact.
examples/angular/query-options-from-a-service/package.json (1)
12-25: Angular and zone.js updates are consistent across the codebase.Angular framework and tooling packages bumped to ^20.3.6, zone.js pinned to 0.15.1, matching patterns in other Angular examples. All updates are patch/minor and fully compatible.
packages/svelte-query-devtools/package.json (1)
50-59: Svelte and TypeScript tooling updates are aligned.@sveltejs/package bumped from 2.4.0 to 2.5.4 (minor range), TypeScript ESLint updated (patches), and Svelte ecosystem aligned with other packages. All updates remain within semver compatibility. Workspace dependencies preserved.
examples/angular/rxjs/package.json (1)
12-25: Angular framework and tooling updates are consistent.Angular packages and tooling aligned to ^20.3.6, zone.js pinned to 0.15.1 - consistent with other Angular examples in this PR. All updates are patch/minor and compatible.
packages/react-query/package.json (1)
73-79: React testing library and build tool updates are reasonable.@testing-library/react (16.1.0 → 16.3.0), @vitejs/plugin-react (4.3.4 → 4.7.0), and npm-run-all2 (5.0.0 → 5.0.2) are all minor/patch updates within semver ranges. Workspace dependencies preserved.
Verify that
@testing-library/react-render-streamat version ^2.0.1 (line 74) is the correct package and version. This appears to be a less common package and should be confirmed as intentional.examples/vue/persister/package.json (1)
15-21: Vue build tooling updates are standard maintenance.idb-keyval (6.2.1 → 6.2.2), @vitejs/plugin-vue (5.2.1 → 5.2.4), and Vite (6.3.6 → 6.4.0) are patch/minor updates within compatible ranges. Low-risk dependency maintenance.
packages/angular-query-experimental/package.json (1)
92-102: Angular packages and tooling updated to stable minor/patch versions.Angular 20.3.6 is the latest patch release for v20, and all related tooling updates are within compatible semver ranges. No issues identified.
packages/query-sync-storage-persister/package.json (1)
67-67: Routine patch update to npm-run-all2.Patch-level bump with no functional impact.
packages/solid-query-persist-client/package.json (1)
73-76: Solid.js ecosystem patches applied consistently.All updates are patch-level increments within compatible semver ranges, coordinated across related Solid packages in this PR.
package.json (2)
8-8: pnpm 10.18.3 is a stable recent patch with bug fixes.pnpm 10.18.3 fixes a bug where pnpm would infinitely recurse when using verifyDepsBeforeInstall with pre/post install scripts. This is a safe upgrade within the v10 series.
43-80: Vite 6.4.0 update is secure and safe to merge.The v6.4.0 release does not list new security advisories, and the relevant security advisory (CVE-2025-58752) was fixed in v6.3.6. Since v6.4.0 is released after v6.3.6, it includes those prior security patches. The update maintains compatibility and poses no security risk.
packages/svelte-query-persist-client/package.json (1)
55-63: Svelte ecosystem updates applied consistently.All updates are minor/patch increments within compatible semver ranges, coordinated across related Svelte packages in this PR.
examples/react/eslint-legacy/package.json (1)
23-23: React tooling updates are compatible patch/minor versions.Vite 6.4.0 is a patch within the v6 series, and @vitejs/plugin-react minor update is backward compatible.
Also applies to: 25-25
examples/react/shadow-dom/package.json (1)
19-19: React tooling updates are compatible patch/minor versions.Vite 6.4.0 is a patch within the v6 series, and @vitejs/plugin-react minor update is backward compatible.
Also applies to: 21-21
examples/react/basic/package.json (1)
23-23: React tooling updates are compatible patch/minor versions.Vite 6.4.0 is a patch within the v6 series, and @vitejs/plugin-react minor update is backward compatible.
Also applies to: 25-25
examples/react/default-query-function/package.json (1)
17-17: DevDependency updates are safe and consistent with broader React example updates in this PR.These are routine minor/patch bumps within the existing version constraints. Vite 6 strives to avoid breaking changes and remains backward compatible, and the @vitejs/plugin-react update is a standard minor version step.
Also applies to: 19-19
examples/react/simple/package.json (1)
17-17: Identical to examples/react/default-query-function/package.json — already reviewed above.Also applies to: 19-19
examples/react/devtools-panel/package.json (1)
17-17: Identical to examples/react/default-query-function/package.json — already reviewed above.Also applies to: 19-19
examples/react/suspense/package.json (1)
19-19: Identical to examples/react/default-query-function/package.json — already reviewed above.Also applies to: 21-21
examples/react/chat/package.json (1)
17-21: DevDependency updates are routine maintenance within consistent version ranges.Tailwind CSS and @tailwindcss/vite patch updates to v4.1.14 are safe incremental improvements, and the core vite/plugin-react updates align with other React examples in this PR. All changes remain within their respective major version constraints.
examples/react/playground/package.json (1)
17-17: Identical to examples/react/default-query-function/package.json — already reviewed above.Also applies to: 19-19
packages/angular-query-persist-client/package.json (1)
60-70: Angular and testing library updates are properly coordinated and safe.The five Angular packages are consistently updated from ^20.0.0 to ^20.3.6 (a minor version bump), which is well-supported by the peerDependencies (>=16.0.0). Testing library and linting tool updates are routine patch/minor bumps. The workspace dependency for @tanstack/query-persist-client-core correctly remains "workspace:*".
examples/react/react-router/package.json (2)
17-20: Runtime dependency updates are within safe version ranges, though react-router version jump warrants a quick compatibility check.
- Lines 17-18: react-router and react-router-dom are consistently updated to ^6.30.1 from ^6.25.1. While this spans five patch versions, it remains within the same minor version (6.x), so breaking changes are not expected. Both packages are updated together, which is the correct approach.
- Line 19: rooks updates from 8.0.0 to 8.4.0, a routine minor version bump within v8.
Run your existing example test suite or manual checks to confirm react-router v6.30.1 works as expected with your router configuration and hooks usage, especially if you rely on any undocumented behavior from v6.25.
26-28: DevDependency updates match other React examples — already reviewed above.examples/angular/basic/package.json (1)
12-19: Angular and zone.js updates look good.Minor/patch version bumps within the Angular 20.x family and zone.js are low-risk and backward compatible. These align with similar updates across other Angular examples in the PR.
Also applies to: 22-24
examples/react/rick-morty/package.json (1)
15-16: React Router and build tooling updates are safe.All dependency bumps are minor/patch versions within their existing constraints. React Router's jump from 6.25.1 to 6.30.1 is a standard minor-version increment with no breaking changes expected.
Also applies to: 19-23
examples/react/react-native/package.json (1)
19-29: Request verification for significant React Native ecosystem bump.The React Native version bump from ^0.76.3 to ^0.82.0 spans five minor versions—this is substantially larger than typical patch/minor updates elsewhere in the PR. React Native historically introduces breaking changes across minor versions, particularly in native module APIs and integration points.
Recommend verifying:
- React Native 0.82.0 release notes for breaking changes
- Compatibility between react-native 0.82.0 and its paired ecosystem packages (gesture-handler 2.28.0, paper 5.14.5, reanimated 3.19.3, safe-area-context 4.14.1, screens 4.17.1, web 0.21.2)
- CI test results to ensure no runtime failures
Also applies to: 32-33
integrations/angular-cli-20/package.json (1)
11-20: Angular and utility library updates are consistent.Angular framework and tooling updates align with other Angular examples in the PR. The tslib bump (2.3.0 → 2.8.1) is a larger minor-version jump but tslib is a stable utility library with strong backward compatibility. All changes remain within established version constraints.
Also applies to: 23-25
examples/react/offline/package.json (1)
16-16: Build and runtime dependency updates are standard.MSW, react-hot-toast, Vite, and Vite React plugin all receive minor/patch updates within established ranges. No compatibility issues expected.
Also applies to: 19-19, 22-22, 24-24
examples/angular/router/package.json (1)
12-16: Angular updates follow consistent pattern.Angular core and tooling bumps (^20.0.0 → ^20.3.6) and zone.js patch (0.15.0 → 0.15.1) align with other Angular examples. Changes are safe and backward compatible.
Minor note: zone.js is pinned with exact version (0.15.1) here and in basic/package.json, but integrations/angular-cli-20/package.json uses a tilde constraint (~0.15.1). This inconsistency is harmless but consider aligning zone.js versioning strategy across the repo if not intentional.
Also applies to: 20-20, 23-25
examples/react/star-wars/package.json (1)
15-16: React tooling and routing updates are standard.Consistent with examples/react/rick-morty/package.json. React Router, Vite, and related dev tooling receive safe minor/patch bumps with no breaking changes expected.
Also applies to: 19-23
| "dependencies": { | ||
| "@tanstack/react-query": "workspace:*", | ||
| "@tanstack/react-query-devtools": "workspace:*", | ||
| "@vitejs/plugin-react": "^4.3.4", | ||
| "@vitejs/plugin-react": "^4.7.0", | ||
| "react": "^19.0.0", | ||
| "react-dom": "^19.0.0", | ||
| "vite": "^6.3.6" | ||
| "vite": "^6.4.0" | ||
| } |
There was a problem hiding this comment.
🧩 Analysis chain
Critical: Vite and plugin are in production dependencies, should be devDependencies.
Build tools like Vite and @vitejs/plugin-react should not be in the dependencies section. They are development-time tooling only and should be moved to devDependencies to avoid bloating the production bundle and violating dependency classification best practices.
Can you confirm whether this is the intended structure for integration packages, or if these should be moved to devDependencies?
🏁 Script executed:
#!/bin/bash
# Check the full package.json content to understand package purpose and metadata
cat integrations/react-vite/package.jsonLength of output: 344
🏁 Script executed:
#!/bin/bash
# List all integration packages to compare structure
find integrations -maxdepth 2 -name package.json -type fLength of output: 351
🏁 Script executed:
#!/bin/bash
# Check structure and purpose of integration packages
for pkg_json in $(find integrations -maxdepth 2 -name package.json -type f); do
echo "=== $pkg_json ==="
# Extract name, private, devDependencies/dependencies sections
jq '.name, .private, (.devDependencies // {} | keys), (.dependencies // {} | keys)' "$pkg_json"
echo ""
doneLength of output: 2200
🏁 Script executed:
#!/bin/bash
# Check if this is a monorepo and understand workspace structure
cat package.json | jq '.workspaces, .name, .private'Length of output: 16
Move Vite and plugin to devDependencies.
Vite and @vitejs/plugin-react are build-time tools only and should be in devDependencies. This aligns with best practices and matches similar integration packages:
react-webpack-4/5: Webpack and Babel plugins in devDependenciesangular-cli-20: Angular CLI tools in devDependenciessvelte-viteandvue-vite: Vite and their respective plugins in devDependencies
Move lines 11 and 14 to a new devDependencies section to fix the misclassification.
🤖 Prompt for AI Agents
integrations/react-vite/package.json lines 8-15: Vite and @vitejs/plugin-react
are declared in "dependencies" but are build-time tools and should be moved to
"devDependencies"; remove the "vite" and "@vitejs/plugin-react" entries from the
"dependencies" object and add a new "devDependencies" object (or merge into an
existing one) containing "@vitejs/plugin-react": "^4.7.0" and "vite": "^6.4.0"
so runtime deps only include react/react-dom and react-query packages.
| "dependencies": { | ||
| "@tanstack/solid-query": "workspace:*", | ||
| "@tanstack/solid-query-devtools": "workspace:*", | ||
| "solid-js": "^1.9.7", | ||
| "vite": "^6.3.6", | ||
| "vite-plugin-solid": "^2.11.6" | ||
| "solid-js": "^1.9.9", | ||
| "vite": "^6.4.0", | ||
| "vite-plugin-solid": "^2.11.9" | ||
| } |
There was a problem hiding this comment.
🧩 Analysis chain
Critical: Vite build tools should be in devDependencies, not dependencies.
Vite and vite-plugin-solid are development-time build tools and should not be in the production dependencies section. Additionally, solid-js placement should be clarified—if this is a build integration package, it may also belong in devDependencies or as a peerDependency rather than a production dependency.
Can you confirm whether this is the intended structure for this integration package, or should Vite-related tools and possibly solid-js be moved to devDependencies or peerDependencies?
I'll verify the structure of this integration package by examining its dependencies across the repository.
🏁 Script executed:
#!/bin/bash
# Find all integration package.json files and extract their dependencies structure
echo "=== Checking integrations package.json files ==="
fd 'package\.json' 'integrations' --exec sh -c 'echo "File: $1"; grep -A 20 '"'"'"dependencies"'"'"' "$1" | head -15' _ {} \;Length of output: 3092
🏁 Script executed:
#!/bin/bash
# Specifically check the solid-vite and react-vite packages mentioned in review
echo "=== integrations/solid-vite/package.json ==="
cat integrations/solid-vite/package.json 2>/dev/null || echo "Not found"
echo -e "\n=== integrations/react-vite/package.json ==="
cat integrations/react-vite/package.json 2>/dev/null || echo "Not found"
echo -e "\n=== Root package.json (workspace info) ==="
cat package.json | head -50Length of output: 3118
🏁 Script executed:
#!/bin/bash
# Check for any documentation about package structure
echo "=== Looking for workspace or integration documentation ==="
find . -maxdepth 2 -name "README*" -o -name "CONTRIBUTING*" | head -10 | xargs grep -l "integration\|devDependencies" 2>/dev/null || echo "No docs found"Length of output: 72
Move vite and vite-plugin-solid to devDependencies.
Vite and vite-plugin-solid are build-time tools and should not be in the production dependencies section. The vue-vite integration package in this repository correctly places vite and its plugin in devDependencies, establishing the standard pattern for integration packages. The solid-js framework dependency can remain in dependencies as it serves the runtime example, but the build tools must be moved.
Note: The same issue affects integrations/react-vite/package.json, which also incorrectly places vite and @vitejs/plugin-react in dependencies.
🤖 Prompt for AI Agents
In integrations/solid-vite/package.json around lines 8 to 14, move the build
tools "vite" and "vite-plugin-solid" out of "dependencies" into
"devDependencies" so they are only installed for development/build time; keep
"solid-js" in "dependencies" as the runtime example. Update the JSON by removing
those two entries from "dependencies" and adding them under a "devDependencies"
object (creating it if missing) with the same versions. Also apply the same
change to integrations/react-vite/package.json for "vite" and
"@vitejs/plugin-react".
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
9396470 to
044f4fa
Compare
There was a problem hiding this comment.
Actionable comments posted: 1
♻️ Duplicate comments (7)
integrations/solid-vite/package.json (1)
8-14: Unresolved: Move vite and vite-plugin-solid to devDependencies.This critical structural issue was previously flagged but remains unresolved. Vite and vite-plugin-solid are build-time tools and should not be in production
dependencies. They must be moved todevDependencies.Apply this diff to fix the dependency placement:
"dependencies": { "@tanstack/solid-query": "workspace:*", "@tanstack/solid-query-devtools": "workspace:*", "solid-js": "^1.9.9" }, "devDependencies": { + "vite": "^6.4.1", + "vite-plugin-solid": "^2.11.9" }examples/angular/rxjs/package.json (1)
12-16: Consistent with coordinated Angular dependency strategy.The updates follow the same pattern as other Angular examples: minor version bump to ^20.3.6 across all Angular packages and exact pin to zone.js 0.15.1. The addition of @angular/forms at ^20.3.6 is appropriate for this RxJS example.
Also applies to: 20-20, 23-25
examples/angular/router/package.json (1)
12-16: Consistent with coordinated Angular dependency strategy.All dependency updates align with the coordinated upgrade pattern across Angular examples.
Also applies to: 20-20, 23-25
examples/angular/simple/package.json (1)
12-15: Consistent with coordinated Angular dependency strategy.All dependency updates align with the coordinated upgrade pattern across Angular examples.
Also applies to: 19-19, 22-24
examples/angular/auto-refetching/package.json (1)
12-15: Consistent with coordinated Angular dependency strategy.All dependency updates align with the coordinated upgrade pattern across Angular examples.
Also applies to: 19-19, 22-24
examples/angular/query-options-from-a-service/package.json (1)
12-16: Consistent with coordinated Angular dependency strategy.All dependency updates align with the coordinated upgrade pattern across Angular examples.
Also applies to: 20-20, 23-25
examples/angular/basic/package.json (1)
12-15: Consistent with coordinated Angular dependency strategy.All dependency updates align with the coordinated upgrade pattern across Angular examples.
Also applies to: 19-19, 22-24
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
⛔ Files ignored due to path filters (1)
pnpm-lock.yamlis excluded by!**/pnpm-lock.yaml
📒 Files selected for processing (79)
examples/angular/auto-refetching/package.json(1 hunks)examples/angular/basic-persister/package.json(1 hunks)examples/angular/basic/package.json(1 hunks)examples/angular/devtools-panel/package.json(1 hunks)examples/angular/infinite-query-with-max-pages/package.json(1 hunks)examples/angular/optimistic-updates/package.json(1 hunks)examples/angular/pagination/package.json(1 hunks)examples/angular/query-options-from-a-service/package.json(1 hunks)examples/angular/router/package.json(1 hunks)examples/angular/rxjs/package.json(1 hunks)examples/angular/simple/package.json(1 hunks)examples/react/algolia/package.json(2 hunks)examples/react/basic-graphql-request/package.json(1 hunks)examples/react/basic/package.json(1 hunks)examples/react/chat/package.json(1 hunks)examples/react/default-query-function/package.json(1 hunks)examples/react/devtools-panel/package.json(1 hunks)examples/react/eslint-legacy/package.json(1 hunks)examples/react/offline/package.json(1 hunks)examples/react/playground/package.json(1 hunks)examples/react/react-native/package.json(1 hunks)examples/react/react-router/package.json(1 hunks)examples/react/rick-morty/package.json(1 hunks)examples/react/shadow-dom/package.json(1 hunks)examples/react/simple/package.json(1 hunks)examples/react/star-wars/package.json(1 hunks)examples/react/suspense/package.json(1 hunks)examples/solid/astro/package.json(1 hunks)examples/solid/basic-graphql-request/package.json(1 hunks)examples/solid/basic/package.json(1 hunks)examples/solid/default-query-function/package.json(1 hunks)examples/solid/simple/package.json(1 hunks)examples/solid/solid-start-streaming/package.json(1 hunks)examples/svelte/auto-refetching/package.json(1 hunks)examples/svelte/basic/package.json(1 hunks)examples/svelte/load-more-infinite-scroll/package.json(1 hunks)examples/svelte/optimistic-updates/package.json(1 hunks)examples/svelte/playground/package.json(1 hunks)examples/svelte/simple/package.json(1 hunks)examples/svelte/ssr/package.json(1 hunks)examples/svelte/star-wars/package.json(1 hunks)examples/vue/2.6-basic/package.json(1 hunks)examples/vue/2.7-basic/package.json(1 hunks)examples/vue/basic/package.json(1 hunks)examples/vue/dependent-queries/package.json(1 hunks)examples/vue/nuxt3/package.json(1 hunks)examples/vue/persister/package.json(1 hunks)examples/vue/simple/package.json(1 hunks)integrations/angular-cli-20/package.json(1 hunks)integrations/react-next-15/package.json(1 hunks)integrations/react-vite/package.json(1 hunks)integrations/react-webpack-4/package.json(1 hunks)integrations/react-webpack-5/package.json(1 hunks)integrations/solid-vite/package.json(1 hunks)integrations/svelte-vite/package.json(1 hunks)integrations/vue-vite/package.json(1 hunks)package.json(3 hunks)packages/angular-query-experimental/package.json(1 hunks)packages/angular-query-persist-client/package.json(1 hunks)packages/eslint-plugin-query/package.json(1 hunks)packages/query-async-storage-persister/package.json(1 hunks)packages/query-broadcast-client-experimental/package.json(1 hunks)packages/query-core/package.json(1 hunks)packages/query-devtools/package.json(1 hunks)packages/query-persist-client-core/package.json(1 hunks)packages/query-sync-storage-persister/package.json(1 hunks)packages/query-test-utils/package.json(1 hunks)packages/react-query-devtools/package.json(1 hunks)packages/react-query-next-experimental/package.json(1 hunks)packages/react-query-persist-client/package.json(1 hunks)packages/react-query/package.json(1 hunks)packages/solid-query-devtools/package.json(1 hunks)packages/solid-query-persist-client/package.json(1 hunks)packages/solid-query/package.json(1 hunks)packages/svelte-query-devtools/package.json(1 hunks)packages/svelte-query-persist-client/package.json(1 hunks)packages/svelte-query/package.json(1 hunks)packages/vue-query-devtools/package.json(1 hunks)packages/vue-query/package.json(1 hunks)
🚧 Files skipped from review as they are similar to previous changes (49)
- examples/react/basic/package.json
- packages/query-persist-client-core/package.json
- examples/svelte/basic/package.json
- examples/angular/pagination/package.json
- examples/react/shadow-dom/package.json
- examples/solid/default-query-function/package.json
- packages/react-query-persist-client/package.json
- examples/react/devtools-panel/package.json
- packages/query-core/package.json
- examples/angular/optimistic-updates/package.json
- integrations/react-webpack-4/package.json
- examples/react/star-wars/package.json
- examples/vue/nuxt3/package.json
- examples/solid/astro/package.json
- packages/query-test-utils/package.json
- packages/solid-query/package.json
- examples/solid/basic-graphql-request/package.json
- packages/react-query-next-experimental/package.json
- examples/react/simple/package.json
- examples/react/react-native/package.json
- examples/react/eslint-legacy/package.json
- examples/svelte/star-wars/package.json
- packages/eslint-plugin-query/package.json
- examples/react/chat/package.json
- integrations/react-webpack-5/package.json
- examples/solid/basic/package.json
- integrations/angular-cli-20/package.json
- examples/vue/2.7-basic/package.json
- integrations/svelte-vite/package.json
- examples/react/basic-graphql-request/package.json
- examples/svelte/auto-refetching/package.json
- examples/vue/basic/package.json
- examples/react/playground/package.json
- packages/react-query-devtools/package.json
- integrations/react-vite/package.json
- packages/angular-query-experimental/package.json
- examples/angular/devtools-panel/package.json
- packages/react-query/package.json
- examples/svelte/optimistic-updates/package.json
- examples/svelte/simple/package.json
- examples/svelte/ssr/package.json
- packages/angular-query-persist-client/package.json
- examples/solid/simple/package.json
- examples/react/default-query-function/package.json
- package.json
- examples/angular/basic-persister/package.json
- packages/svelte-query-devtools/package.json
- packages/solid-query-persist-client/package.json
- packages/query-devtools/package.json
🧰 Additional context used
🧠 Learnings (1)
📚 Learning: 2025-09-02T17:57:33.184Z
Learnt from: TkDodo
PR: TanStack/query#9612
File: packages/query-async-storage-persister/src/asyncThrottle.ts:0-0
Timestamp: 2025-09-02T17:57:33.184Z
Learning: When importing from tanstack/query-core in other TanStack Query packages like query-async-storage-persister, a workspace dependency "tanstack/query-core": "workspace:*" needs to be added to the package.json.
Applied to files:
packages/vue-query-devtools/package.jsonpackages/svelte-query/package.jsonintegrations/solid-vite/package.jsonpackages/query-async-storage-persister/package.jsonpackages/query-sync-storage-persister/package.jsonpackages/query-broadcast-client-experimental/package.jsonintegrations/react-next-15/package.jsonpackages/svelte-query-persist-client/package.json
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)
- GitHub Check: Preview
- GitHub Check: Test
🔇 Additional comments (26)
integrations/react-next-15/package.json (1)
9-9: Minor version bump for @js-temporal/polyfill looks good.The update from
^0.4.4to^0.5.1is a straightforward minor version bump consistent with the PR's objective to update non-major dependencies. Workspace dependencies remain correctly configured.packages/query-broadcast-client-experimental/package.json (1)
60-68: Dependency updates look good.All version bumps are minor/patch updates within semver constraints—low-risk maintenance. The workspace dependency for
@tanstack/query-coreis correctly in place, and dev tooling updates are standard.packages/query-async-storage-persister/package.json (1)
67-67: Routine patch version update.The bump of
npm-run-all2from^5.0.2is a safe, backward-compatible patch update consistent with the PR objectives. Workspace dependencies remain properly configured.examples/svelte/load-more-infinite-scroll/package.json (1)
15-21: DevDependency updates align with PR scope.All changes are non-major updates using caret ranges (minor/patch bumps), affecting only build tooling with no impact on runtime behavior or public APIs.
examples/svelte/playground/package.json (1)
15-21: DevDependency updates align with PR scope.Identical non-major updates to load-more-infinite-scroll example, maintaining consistency across Svelte examples with caret-ranged minor/patch version bumps for build tooling only.
packages/vue-query/package.json (1)
66-66: Dependency updates are consistent and appropriately scoped.Both updates are patch-level version bumps:
@vue/devtools-api: 6.6.3 → 6.6.4 (patch)eslint-plugin-vue: 10.5.0 → 10.5.1 (patch)The
eslint-plugin-vuebump is consistent with the corresponding update inpackages/vue-query-devtools/package.json. Patch-level updates are generally safe and backwards compatible.Please ensure that the build and type-checking steps pass with these updated versions (e.g.,
pnpm run test:eslint,pnpm run compile).Also applies to: 73-73
packages/vue-query-devtools/package.json (2)
58-58:eslint-plugin-vuepatch update is consistent.The update from 10.5.0 to 10.5.1 matches the corresponding update in
packages/vue-query/package.jsonand is a safe patch-level bump.
60-60: Verifyviteminor version bump in build process.The update from 6.3.6 to 6.4.1 is a minor version bump that affects the build tool used in the
buildscript (line 23:pnpm run compile && vite build). While minor-version updates should be backwards compatible, build tools can sometimes introduce subtle behavioral changes or configuration requirements.Please confirm that:
- The build process (
pnpm run compile && vite build) completes successfully with vite 6.4.1- Type checking and linting pass (test:eslint, test:types)
- There are no new warnings or deprecations introduced by vite 6.4.1
packages/svelte-query/package.json (1)
55-55: Svelte tooling devDependencies updated consistently.All four devDependency bumps are minor/patch updates (non-breaking) that modernize the Svelte compiler and linter toolchain. Runtime and workspace dependencies remain unchanged, and the caret ranges properly constrain future updates to compatible versions.
Also applies to: 59-59, 60-60, 61-61, 62-62
packages/svelte-query-persist-client/package.json (1)
55-55: Svelte tooling devDependencies synchronized with related packages.The updates mirror those in
packages/svelte-query/package.json, maintaining consistency across the Svelte package ecosystem within the monorepo. All four devDependency bumps are non-major, and workspace/peer dependencies remain unchanged. Based on learnings from prior reviews, workspace dependencies are properly preserved.Also applies to: 60-60, 61-61, 62-62, 63-63
packages/solid-query-devtools/package.json (1)
71-74: Dependency updates look good.All updates are patch/minor version bumps within safe ranges. The solid-js update (^1.9.9) satisfies the peer dependency constraint (^1.6.0). Consistent with Solid-related updates across the PR.
examples/solid/solid-start-streaming/package.json (1)
14-18: Dependency updates are reasonable for a non-major release cycle.The @solidjs/start minor version bump (^1.1.3 → ^1.2.0) falls within non-major scope. solid-js and vinxi updates are safe. Ensure the streaming example is tested post-merge to confirm compatibility.
packages/query-sync-storage-persister/package.json (1)
67-67: Safe patch version update.The npm-run-all2 patch bump (^5.0.0 → ^5.0.2) is low-risk and backward-compatible. Consistent with similar updates across other packages in the monorepo.
examples/react/react-router/package.json (1)
17-19: Dependency updates look good.All version bumps are within semantic versioning constraints and represent standard non-major updates. Vite 6 largely maintains backward compatibility, and developers building a single-page application will see no change to their workflow. No compatibility concerns for these routine updates.
Also applies to: 26-26, 28-28
examples/react/rick-morty/package.json (1)
15-16: Dependency updates look good.All version bumps are within semantic versioning constraints. The tailwindcss ecosystem patch updates (4.1.13 → 4.1.14) and react-router minor updates maintain compatibility. Vite 6 largely maintains backward compatibility for single-page applications. No concerns for these routine updates.
Also applies to: 19-21, 23-23
examples/react/algolia/package.json (3)
11-11: Verify @algolia/client-search 5.40.1 compatibility and confirm pinned version is intentional.The dependency was updated from a caret range (allowing minor updates) to an exact version (5.40.1). This represents a significant jump from 5.2.1 and introduces stricter pinning. While within v5.x and likely backward compatible, ensure:
- The example code works correctly with 5.40.1
- The exact version pin (rather than caret range) is intentional—if you want flexibility for future patches, consider
^5.40.1- Any API changes between 5.2.1 and 5.40.1 are accounted for
21-21: Vite plugin React bump is safe.The update from ^4.3.4 to ^4.7.0 is a standard minor bump with the caret preserved. This should be compatible with vite ^6.4.1 and poses no compatibility risks.
23-23: Vite patch/minor bump is safe.The update from ^6.3.6 to ^6.4.1 is a conservative patch/minor version bump with the caret preserved. This maintains compatibility with @vitejs/plugin-react and poses no risks.
examples/vue/dependent-queries/package.json (1)
15-15: Version updates are safe and consistent with related Vue examples.@vitejs/plugin-vue v5.2.1+ supports Vite v6, and both updates represent patch-level improvements. These changes are consistent across Vue examples in the PR.
Also applies to: 17-17
integrations/vue-vite/package.json (1)
13-13: Version updates align with broader Vue tooling consistency across the PR.Patch-level updates to Vite and its Vue plugin are straightforward and match updates in related integration files.
Also applies to: 15-15
examples/vue/2.6-basic/package.json (1)
11-11: @tanstack/vue-query patch update is appropriate.Patch-level bump from 5.90.2 to 5.90.5 is consistent with this library's release cadence and aligns with updates in other Vue example configurations.
examples/vue/simple/package.json (1)
16-16: Version updates maintain consistency across Vue examples.Patch-level updates to Vite and plugin-vue follow the pattern applied across other Vue example configurations in this PR.
Also applies to: 18-18
examples/vue/persister/package.json (1)
15-15: All dependency updates are safe patch-level improvements.idb-keyval 6.2.2 is the latest version, and the Vite tooling updates are consistent with other Vue examples. All caret ranges are preserved, and no breaking changes are expected.
Also applies to: 19-19, 21-21
examples/react/offline/package.json (2)
22-22: Verify Vite and @vitejs/plugin-react compatibility with React 19.The build tooling has been updated (Vite ^6.3.6 → ^6.4.1, @vitejs/plugin-react ^4.3.4 → ^4.7.0) alongside React ^19.0.0. Confirm that the updated Vite plugin is fully compatible with React 19's JSX transform and that the build pipeline works as expected for this offline example.
Also applies to: 24-24
16-16: Looking at the web search results, I can now provide verification based on the findings:Version 2.0 brings the biggest API change to the library since its inception. Alongside the new API, it includes various features, such as ReadableStream support, ESM-compatibility, and countless bug fixes. However, these breaking changes occurred when migrating from MSW 1.x to 2.x.
The update in this PR moves from msw ^2.6.6 to ^2.11.6—both within the 2.x series. Versions between 2.6.6 and 2.11.6 (2.6.7–2.7.0 and beyond) are listed as incremental releases, indicating patch and minor updates without major API rework. Semver guarantees backward compatibility within the same major version, so no breaking changes are expected between these versions.
No breaking changes identified between msw 2.6.6 and 2.11.6.
Both versions are within the 2.x stable series; the bump spans minor and patch releases only. The breaking changes documented in MSW literature relate to the 1.x → 2.0 migration, not within the 2.x range. Verify that the example code uses only stable, non-deprecated APIs—code written for 2.6.6 should work unchanged with 2.11.6.
examples/react/suspense/package.json (1)
19-19: Safe version bumps, but @vitejs/plugin-react 4.7.0 has reported issues—test the build.Both updates are minor/patch bumps to build tooling. Vite 6.4.1 has no new public security CVEs, though it introduced stricter dev-server host/file protections that have caused breaking behaviour for some users in specific setups (docker/hostname mismatches).
However, @vitejs/plugin-react 4.7.0 has reported issues including JSX runtime auto-upgrades breaking builds, react/jsx-runtime import errors, and runtime selection changes. These are conditional (specific setups/patterns), not automatic failures, but since this is an example project that must build and run, verify the suspense example builds and runs without issues after the update.
| "@angular/common": "^20.3.6", | ||
| "@angular/compiler": "^20.3.6", | ||
| "@angular/core": "^20.3.6", | ||
| "@angular/platform-browser": "^20.3.6", |
There was a problem hiding this comment.
🧩 Analysis chain
Verify Angular 20.3.6 and zone.js 0.15.1 compatibility.
The Angular dependencies are being updated from ^20.0.0 to ^20.3.6, and zone.js from 0.15.0 to 0.15.1. While these are minor/patch updates within the same major version, verify that zone.js 0.15.1 maintains compatibility with Angular 20.3.6 and check the release notes for any breaking changes or compatibility notes.
Also applies to: 19-19, 22-24
🌐 Web query:
Are there any known compatibility issues between Angular 20.3.6 and zone.js 0.15.1?
💡 Result:
Short answer: Yes—not usually a runtime bug, but there are known peer-dependency/compatibility constraints. Several projects and discussions report npm/ERESOLVE or peerDependency mismatches when trying to install zone.js 0.15.x alongside recent Angular releases (Angular expects zone.js in a <0.15 range for many packages), so you can hit install/resolve errors or tooling warnings even if the app might run. See examples/discussion threads. [1][2][3]
If you want, tell me your package.json and npm/yarn/pnpm output and I’ll show exactly why your install is failing and how to fix it (force-resolutions, align versions, or use the zoneless option).
🏁 Script executed:
#!/bin/bash
# Examine the package.json file to check versions and peer dependencies
cat examples/angular/infinite-query-with-max-pages/package.jsonLength of output: 715
🏁 Script executed:
#!/bin/bash
# Check if there's a package-lock.json or pnpm-lock.yaml that shows resolution details
ls -la examples/angular/infinite-query-with-max-pages/ | grep -E "package-lock|pnpm-lock|yarn.lock"Length of output: 0
🏁 Script executed:
#!/bin/bash
# Search for zone.js version specifications and peer dependencies across Angular configs
rg -n "zone\.js|peerDependencies" examples/angular/infinite-query-with-max-pages/ -A2 -B2Length of output: 960
🏁 Script executed:
#!/bin/bash
# Check the root package.json or any shared configs for zone.js constraints
rg -n "zone\.js" . --type=json -C3 | head -50Length of output: 3425
---
🌐 Web query:
```web
Angular 20.3.6 zone.js peer dependency version requirement specification
💡 Result:
Do you want me to fetch the exact peerDependency string from the @angular/* 20.3.6 package.json (I can retrieve and paste the exact "zone.js" requirement)?
---
🌐 Web query:
```web
Angular 20.3.6 npm package peerDependencies zone.js
💡 Result:
Short answer: Angular 20.x expects zone.js v0.14.x as the peer dependency (install e.g. zone.js@^0.14.2 / ~0.14.x). Install with: npm install --save zone.js@^0.14.2. [1][2]
Sources:
- discussion showing packages targeting zone.js ^0.14.2. [1]
- zone.js npm registry (v0.14.2 information). [2]
Update zone.js to ^0.14.2 for Angular 20.3.6 compatibility.
Angular 20.x expects zone.js v0.14.x as the peer dependency, but zone.js is pinned to 0.15.1. This will cause peerDependency conflicts during installation. Update to zone.js ^0.14.2 or ~0.14.x across all Angular examples (lines 19 in: infinite-query-with-max-pages, simple, rxjs, devtools-panel, and router package.json files).
🤖 Prompt for AI Agents
In examples/angular/infinite-query-with-max-pages/package.json around lines 12
to 15, zone.js is pinned to an incompatible version (0.15.1) for Angular 20.3.6;
update the zone.js dependency to "^0.14.2" (or "~0.14.x") in this package.json
(line ~19) and apply the same change to the other Angular example package.json
files mentioned (simple, rxjs, devtools-panel, router) so they all use zone.js
^0.14.2, then run install/build to verify no peerDependency conflicts.
044f4fa to
3b87487
Compare
This PR contains the following updates:
5.2.1->5.40.1^20.0.0->^20.3.6^20.0.0->^20.3.6^20.0.0->^20.3.6^20.0.0->^20.3.6^20.0.0->^20.3.6^20.0.0->^20.3.6^20.0.0->^20.3.6^20.0.0->^20.3.6^20.0.0->^20.3.6^20.0.0->^20.3.6^0.15.3->^0.18.2^5.0.7->^5.1.1^8.1.3->^8.2.10^7.26.0->^7.28.4^7.24.9->^7.28.4^7.26.0->^7.28.3^7.25.9->^7.27.1^2.29.5->^2.29.7^2.0.1->^2.2.2^10.0.5->^10.0.11^0.4.4->^0.5.1^0.13.4->^0.13.11^1.2.2->^1.5.2^2.0.26->^2.1.3^1.1.3->^1.2.0^6.1.0->^6.1.1^2.42.2->^2.47.2^2.4.0->^2.5.4^4.1.13->^4.1.14^4.0.14->^4.1.14^0.20.2->^0.22.0^5.90.2->^5.90.5^18.0.0->^18.1.0^10.4.0->^10.4.1^6.8.0->^6.9.1^16.1.0->^16.3.0^2.0.0->^2.0.1^5.0.4->^5.0.5^8.44.1->^8.46.1^8.44.1->^8.46.1^8.44.1->^8.46.1^4.3.4->^4.7.0^5.2.1->^5.2.4^1.1.36->^1.3.23^6.6.3->^6.6.4^8.3.0->^8.4.1^7.0.0->^7.1.0^9.36.0->^9.38.0^50.5.0->^50.8.0^3.11.0->^3.12.5^10.5.0->^10.5.1^1.2.1->^1.2.2^52.0.11->^52.0.47^17.0.3->^17.1.7^2.0.0->^2.2.3^2.1.16->^2.1.18^16.9.0->^16.11.0^7.1.2->^7.3.1^5.6.3->^5.6.4^6.2.1->^6.2.2^27.0.0->^27.0.1^5.63.1->^5.66.1^2.6.6->^2.11.6^5.0.0->^5.0.2^3.12.4->^3.19.321.5.3->21.6.510.17.0->10.18.3^0.3.13->^0.3.15^2.5.2->^2.6.0^0.76.3->^0.82.0^2.20.2->^2.28.0^5.12.5->^5.14.5^3.16.2->^3.19.3^4.12.0->^4.14.1^4.1.0->^4.17.1^0.19.13->^0.21.2^6.25.1->^6.30.1^6.25.1->^6.30.1^8.0.0->^8.4.0~7.8.0->~7.8.2^1.9.7->^1.9.9^0.2.3->^0.3.0^5.39.3->^5.41.0^4.3.1->^4.3.3^4.1.13->^4.1.14^3.4.7->^3.4.18^4.0.14->^4.1.14^2.3.0->^2.8.1^0.5.3->^0.5.8^6.3.6->^6.4.14.2.3->4.5.4^0.9.0->^0.10.0^2.11.6->^2.11.9~0.15.0->~0.15.10.15.0->0.15.1Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
algolia/algoliasearch-client-javascript (@algolia/client-search)
v5.40.1Compare Source
v5.40.0Compare Source
v5.39.0Compare Source
v5.38.0Compare Source
composition&composition-full(#5333) by @ClaraMullerv5.37.0Compare Source
Configuration
📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ 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.
Summary by CodeRabbit