chore: bump deps #6408
chore: bump deps #6408
Conversation
📝 WalkthroughWalkthroughBumped Vite from ^7.1.7 → ^7.3.1 across many package.json files; upgraded versions in root package.json (pnpm, tooling, libs); removed several Vite/Vitest type assertions; widespread TypeScript formatting/reflow of generic/type signatures (no semantic changes). One functional change: solid-router Route.useNavigate now uses this.fullPath directly. Changes
Sequence Diagram(s)(Skipped — changes are mostly formatting and dependency bumps; only one small internal navigation adjustment, not suitable for multi-component sequential visualization.) Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Possibly related PRs
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches
Comment |
|
View your CI Pipeline Execution ↗ for commit 79ddd48
☁️ Nx Cloud last updated this comment at |
github-actions
bot
added
documentation
schiller-manuel
force-pushed
the
bump-deps
branch
from
cbac34f to
fca8650
Compare
schiller-manuel
force-pushed
the
bump-deps
branch
from
fb4e640 to
8d675c9
Compare
schiller-manuel
force-pushed
the
bump-deps
branch
from
8d675c9 to
7f78186
Compare
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 16
🤖 Fix all issues with AI agents
In `@e2e/solid-router/basic-scroll-restoration/package.json`:
- Line 25: The package.json currently pins Vite to "vite": "^7.3.1", which is
incompatible with vite-plugin-solid; update the dependency to a Vite 6.x version
(e.g., change the "vite" entry from "^7.3.1" to a 6.x range like "^6.0.0" or a
specific 6.x release) so the e2e test uses a Vite version supported by
vite-plugin-solid, then run install to verify the plugin resolves correctly.
In `@e2e/solid-router/sentry-integration/package.json`:
- Line 28: Summary: The PR updated the package.json dependency "vite" to
"^7.3.1" which is incompatible with vite-plugin-solid; revert to Vite 6.x to
avoid breaking the e2e app. Fix: in package.json restore the "vite" entry back
to a Vite 6.x range compatible with vite-plugin-solid (e.g., "^6.x"), ensure you
do not change other deps, run your package manager to reinstall, and run the e2e
tests; if you plan to upgrade later, wait for vite-plugin-solid Vite 7 support,
verify Node.js meets Vite 7 requirements (20.19+ or 22.12+), and test
`@sentry/vite-plugin` compatibility before bumping.
In `@e2e/solid-start/query-integration/package.json`:
- Line 23: Restore the Vite dependency to a Vite 6-compatible version instead of
"vite": "^7.3.1" in package.json; update the "vite" entry back to the previous
6.x constraint (e.g., "^6.0.0" or the project's prior pinned 6.x version) so it
matches peerDependency requirements of `@tailwindcss/vite` and compatibility
expectations of vite-plugin-solid.
In `@e2e/vue-router/basic-vue-query/package.json`:
- Line 29: package.json currently pins Vite to "^7.3.1" which is incompatible
with `@vitejs/plugin-vue`@5.2.3 and `@vitejs/plugin-vue-jsx`@4.1.2; update
package.json by either downgrading the "vite" entry to a 6.x range (e.g.,
"^6.0.0") or upgrade the plugins to versions that support Vite 7 (e.g., set
`@vitejs/plugin-vue` to 6.x and `@vitejs/plugin-vue-jsx` to 5.x) so peerDependencies
align; adjust the dependency lines for "vite", "@vitejs/plugin-vue", and
"@vitejs/plugin-vue-jsx" in package.json and run install to verify no peer
dependency warnings.
In `@e2e/vue-router/generator-cli-only/package.json`:
- Line 28: The package.json currently upgrades the vite dependency to "vite":
"^7.3.1" but the Vue plugins are still on incompatible major versions; update
`@vitejs/plugin-vue` to a 6.x release (e.g., v6.0.3) and `@vitejs/plugin-vue-jsx` to
a 5.x release so they declare peer support for Vite 7+, then update the
package.json dependency entries for "@vitejs/plugin-vue" and
"@vitejs/plugin-vue-jsx", regenerate the lockfile (npm/yarn/pnpm install) and
run the test/build step to verify no peer-dependency conflicts remain.
In `@e2e/vue-router/sentry-integration/package.json`:
- Line 29: The package.json currently pins "vite": "^7.3.1" while
`@vitejs/plugin-vue-jsx` is at 4.1.2 which only supports Vite ^5/6; update the
dependency `@vitejs/plugin-vue-jsx` in package.json to a Vite 7-compatible release
(bump to a 5.x or later version, e.g., ^5.0.0) so the plugin matches Vite 7;
ensure package.json's dependencies/devDependencies entry for
"@vitejs/plugin-vue-jsx" is updated and run install to verify compatibility.
In `@examples/react/basic-virtual-inside-file-based/package.json`:
- Line 28: The package.json currently bumps "vite" to ^7.3.1 which is
incompatible with the pinned plugins; update dependencies together: set "vite"
back to a supported version (or upgrade `@vitejs/plugin-react` and
`@tailwindcss/vite` alongside it), specifically ensure `@vitejs/plugin-react` is
upgraded to a 5.x+ release that declares Vite 7 support and bump
`@tailwindcss/vite` to >=4.1.11, and update the package.json "engines" (Node) to
require Node 20.19+ or 22.12+ if you keep Vite 7; change the versions for the
symbols "vite", "@vitejs/plugin-react", and "@tailwindcss/vite" in package.json
to matching compatible versions and run install to verify no peer dependency
conflicts.
In `@examples/react/router-monorepo-simple-lazy/packages/app/package.json`:
- Line 24: Update the `@vitejs/plugin-react` dependency in package.json to a 4.x
release that officially supports Vite 7 (or the latest 4.x available) to avoid
peer-dependency warnings; locate the "dependencies" / "devDependencies" entry
for "@vitejs/plugin-react" in packages/app/package.json and bump its version
string to a Vite-7-compatible 4.x release (or use the latest stable 4.x) and
then run install to regenerate lockfiles.
In `@examples/react/start-workos/package.json`:
- Line 31: Update the `@vitejs/plugin-react` dependency to v5 to match Vite 7.3.1:
open package.json and replace the current "@vitejs/plugin-react": "^4.3.4" entry
with the v5 version (for example "^5.0.0" or the latest v5.x), then run your
package manager install and test the dev/build commands to ensure compatibility
with Vite 7.3.1.
In `@examples/solid/basic-default-search-params/package.json`:
- Line 24: Replace the Vite dependency in package.json that currently reads
"vite": "^7.3.1" with a Vite 6.x version compatible with vite-plugin-solid
(e.g., a latest 6.x minor such as "^6.16.x"); update package.json accordingly,
delete or regenerate lockfile (package-lock.json or yarn.lock), and run your
package manager install to ensure the project uses the downgraded Vite so the
SolidJS example builds with vite-plugin-solid.
In `@examples/solid/basic-virtual-inside-file-based/package.json`:
- Line 25: The package.json dependency "vite" is set to an incompatible v7.x;
change the "vite" entry to a Vite 6.x range (e.g., "^6.0.0" or the latest v6
patch) so it matches supported versions of vite-plugin-solid v2.11.x;
additionally, if vite-plugin-solid is an internal/workspace package, ensure its
package.json uses the workspace:* protocol for the dependency instead of a fixed
version.
In `@examples/solid/router-monorepo-solid-query/packages/app/package.json`:
- Line 22: The package.json currently pins "vite": "^7.3.1" which is
incompatible with the installed "@tailwindcss/vite" v4.1.18 peer dependency;
update package.json to resolve the peer conflict by either downgrading the
"vite" version to a 6.x range (e.g., "^6.0.0") or upgrading the
"@tailwindcss/vite" dependency to a release that explicitly supports Vite 7,
ensuring the change is applied to the "vite" and/or "@tailwindcss/vite" entries
so npm/yarn no longer reports a peer dependency mismatch.
In `@examples/solid/start-counter/package.json`:
- Line 26: Update the vite-tsconfig-paths dependency to a Vite 7–compatible
release (upgrade from "vite-tsconfig-paths" v5.1.4 to v6.x) in package.json so
it explicitly supports Vite 7. Alternatively, if you choose not to upgrade, run
a compatibility test with the current "vite-tsconfig-paths" version against Vite
7.3.1 and document the result; prefer changing the dependency entry in
package.json to "vite-tsconfig-paths": "^6.0.0" to ensure guaranteed
compatibility with vite and vite-plugin-solid.
In `@examples/solid/start-supabase-basic/package.json`:
- Line 28: The package.json currently pins "vite": "^7.3.1" which is
incompatible with `@tailwindcss/vite`@4.1.18 (peerDependency ^5.2.0 || ^6) and
with vite-plugin-solid’s unstable Vite 7 support; either change the Vite entry
in package.json to a 6.x range (e.g., "vite": "^6.0.0") to match
`@tailwindcss/vite`@4.1.18, or instead update the plugin dependencies
(`@tailwindcss/vite` and vite-plugin-solid) to versions that explicitly support
Vite 7; locate the "vite" field in package.json and make one consistent change
(downgrade Vite to ^6.x or upgrade the two plugins) and then run npm/yarn
install to verify peerDependency resolution.
In `@examples/solid/view-transitions/package.json`:
- Line 24: Revert the Vite version bump in package.json: change the "vite"
dependency back to a Vite 6.x release compatible with vite-plugin-solid (use the
latest 6.x semver range, e.g. ^6.x) and update lockfiles (run npm/yarn install)
so the project uses a Vite 6-compatible install; ensure vite-plugin-solid
remains at a version that supports Vite 6.
In `@packages/router-devtools-core/package.json`:
- Line 71: Update the package.json engines.node constraint to match Vite 7.3.1's
minimum Node version requirement by replacing the current "engines.node" value
with a more restrictive constraint such as ">=20.19" (or ">=20.19 || >=22.12" if
you prefer to express both lines), ensuring it aligns with the declared
dependency "vite": "^7.3.1"; leave vite-plugin-solid as-is since it's
compatible.
♻️ Duplicate comments (15)
examples/react/router-monorepo-simple/packages/post-feature/package.json (1)
20-20: Same Vite bump—apply the same compatibility check.This is the same Vite 7.3.1 update; please apply the same compatibility verification noted earlier.
examples/react/deferred-data/package.json (1)
26-26: Same Vite bump—apply the same compatibility check.This is the same Vite 7.3.1 update; please apply the same compatibility verification noted earlier.
examples/solid/router-monorepo-solid-query/package.json (1)
25-25: Same Vite bump—apply the same compatibility check.This is the same Vite 7.3.1 update; please apply the same compatibility verification noted earlier.
e2e/react-router/basic-file-based-code-splitting/package.json (1)
31-31: Same Vite bump—apply the same compatibility check.This is the same Vite 7.3.1 update; please apply the same compatibility verification noted earlier.
e2e/solid-start/selective-ssr/package.json (1)
26-26: Same Vite bump—apply the same compatibility check.This is the same Vite 7.3.1 update; please apply the same compatibility verification noted earlier.
examples/solid/start-large/package.json (1)
30-30: Vite bump — same compatibility verification as earlier.
Please apply the same Vite 7.3.1 release-note/plugin-compatibility verification noted above.examples/solid/start-basic-static/package.json (1)
25-25: Vite bump — same compatibility verification as earlier.
Please apply the same Vite 7.3.1 release-note/plugin-compatibility verification noted above.examples/react/basic/package.json (1)
25-25: Vite bump — same compatibility verification as earlier.
Please apply the same Vite 7.3.1 release-note/plugin-compatibility verification noted above (including@vitejs/plugin-react).packages/solid-router-devtools/package.json (1)
73-73: Vite bump — same compatibility verification as earlier.
Please apply the same Vite 7.3.1 release-note/plugin-compatibility verification noted above.examples/solid/start-basic-netlify/package.json (1)
23-23: Vite bump — same compatibility verification as earlier.
Please apply the same Vite 7.3.1 release-note/plugin-compatibility verification noted above (including the Netlify plugin).e2e/react-start/basic-tsr-config/package.json (1)
18-18: Same Vite 7.3.1 verification applies here.Please align this bump with the Vite 7.3.1 release notes and plugin peer ranges as noted earlier.
examples/solid/router-monorepo-solid-query/packages/post-feature/package.json (1)
19-19: Same Vite 7.3.1 verification applies here.Please confirm the bump against Vite 7.3.1 release notes and plugin peer ranges (e.g., vite-plugin-solid, vite-plugin-dts).
e2e/vue-router/basic-virtual-named-export-config-file-based/package.json (1)
31-31: Same Vite 7.3.1 verification applies here.Please ensure the 7.3.1 bump aligns with
@vitejs/plugin-vueand@vitejs/plugin-vue-jsxpeer requirements.e2e/react-start/selective-ssr/package.json (1)
20-20: Same Vite 7.3.1 verification applies here.Please confirm the bump against Vite 7.3.1 release notes and
@vitejs/plugin-reactpeer ranges.e2e/react-start/serialization-adapters/package.json (1)
20-20: Same Vite 7.3.1 verification applies here.Please confirm the bump against Vite 7.3.1 release notes and
@vitejs/plugin-reactpeer ranges.
| "@playwright/test": "^1.50.1", | ||
| "@tanstack/router-e2e-utils": "workspace:^", | ||
| "vite": "^7.1.7", | ||
| "vite": "^7.3.1", |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
Vite 7.3.1 release notes breaking changes
💡 Result:
There are no breaking changes listed for Vite v7.3.1 — it’s a patch release. See the package release/changelog references for v7.3.1. [1][2]
Sources:
[1] vite package.json (v7.3.1) on unpkg.
[2] Source/changes listing referencing packages/vite/CHANGELOG.md for v7.3.1.
🌐 Web query:
vite-plugin-solid compatibility Vite 7.3.1
💡 Result:
Short answer: Not yet officially—vite-plugin-solid does not currently advertise full Vite 7 compatibility and there are open issues requesting Vite 7 support. You may get some things working, but expect breakage until the plugin is updated for Vite 7. [1][2][3]
Sources:
- Vite 7 announcement (June 24, 2025). [1]
- solidjs/vite-plugin-solid GitHub repo. [2]
- Open issue requesting Vite 7 support in the plugin repo. [3]
🏁 Script executed:
cat -n e2e/solid-router/basic-scroll-restoration/package.jsonRepository: TanStack/router
Length of output: 174
Vite 7.3.1 is not yet supported by vite-plugin-solid.
Vite 7.x compatibility is not advertised for vite-plugin-solid, and the plugin has open issues requesting Vite 7 support. Using Vite 7.3.1 in this e2e test will cause breakage. Either downgrade to Vite 6.x or wait for vite-plugin-solid to be updated for Vite 7.
🤖 Prompt for AI Agents
In `@e2e/solid-router/basic-scroll-restoration/package.json` at line 25, The
package.json currently pins Vite to "vite": "^7.3.1", which is incompatible with
vite-plugin-solid; update the dependency to a Vite 6.x version (e.g., change the
"vite" entry from "^7.3.1" to a 6.x range like "^6.0.0" or a specific 6.x
release) so the e2e test uses a Vite version supported by vite-plugin-solid,
then run install to verify the plugin resolves correctly.
| "@tanstack/router-e2e-utils": "workspace:^", | ||
| "vite-plugin-solid": "^2.11.10", | ||
| "vite": "^7.1.7" | ||
| "vite": "^7.3.1" |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
cat -n "e2e/solid-router/sentry-integration/package.json"Repository: TanStack/router
Length of output: 174
🌐 Web query:
Vite 7.3.1 release notes breaking changes compatibility
💡 Result:
Summary of breaking changes & compatibility for Vite 7 (including v7.3.1)
- Node.js: Vite 7 requires Node 20.19+ or 22.12+ (Node 18 dropped). [1]
- Distribution: Vite 7 is ESM‑only (CJS consumers must use compatible Node versions / require(esm)). [1]
- Browser targets: default build target changed to "baseline-widely-available" with raised minimum browser versions (e.g. Chrome 107+, Safari 16+). This may change transpilation/output compared with Vite 6. [1]
- Migration notes / breaking APIs: several planned/considered breaking changes (hooks API, HMR hotUpdate hook, SSR ModuleRunner, per‑environment APIs, shared plugins during build) are documented on the Vite Breaking Changes / Migration pages; some removals/changes may be opt‑in via the future option. Check the Migration guide for concrete code changes (e.g. import.meta.hot.accept URL→id, legacy chunk/rolldown notes). [2][4]
- Ecosystem/plugin compatibility: some plugins needed peer‑dependency updates (example:
@tailwindcss/vitehad a strict peer range causing install errors with Vite 7 until plugin updates). Expect to check plugin peer deps when upgrading. [3] - v7.3.1 specifics: see the package CHANGELOG at the v7.3.1 tag for the exact patch fixes and notes. If you need the full v7.3.1 entry (changelog + patch details), check the repo CHANGELOG.md for tag v7.3.1. [4]
Recommendations
- Verify Node version (>=20.19 or >=22.12) on CI/dev machines before upgrading. [1]
- Run dependency/install tests (pnpm/npm/yarn) to catch peer‑dependency issues in plugins (Tailwind, etc.). [3]
- Read the v7 migration guide and the v7.3.1 changelog on GitHub for any patch‑specific fixes before upgrading. [2][4]
Sources
[1] Vite 7 announcement (Node/browser targets, ESM): vite.dev blog. (vite.dev)
[2] Vite Breaking Changes / Migration guidance: vite.dev (Changes & Migration pages). (vite.dev)
[3] Plugin compatibility example (Tailwind peer dep issue): vitejs/vite GitHub issue. (github.com)
[4] v7.3.1 package changelog (repo tag): vite GitHub (packages/vite CHANGELOG.md at v7.3.1). (github.com)
If you want, I can open the v7.3.1 changelog and paste the exact patch notes relevant to your project.
Citations:
- 1: https://vite.dev/blog/announcing-vite7?utm_source=openai
- 2: https://vite.dev/changes/?utm_source=openai
- 3: Vite 7 incompatible with @tailwindcss/vite due to strict peer dependency (^5.2.0 || ^6) vitejs/vite#20284
- 4: https://github.com/vitejs/vite/blob/v7.3.1/packages/vite/CHANGELOG.md
🏁 Script executed:
# Check if this is part of a monorepo/workspace
find . -maxdepth 2 -name "package.json" -type f | head -20Repository: TanStack/router
Length of output: 174
🏁 Script executed:
# Search for package.json files in the repository to understand structure
git ls-files "**/package.json" | grep -E "(solid-router|sentry)" | head -20Repository: TanStack/router
Length of output: 174
🌐 Web query:
@sentry/vite-plugin Vite 7 compatibility support
💡 Result:
Short answer: There’s no official announcement that @sentry/vite-plugin explicitly targets Vite 7; Sentry’s bundler-plugins repo is still the canonical source and their docs recommend using up-to-date bundler-plugin releases (and upgrading bundler-plugin versions to avoid SDK v7/v8 mismatches). If you plan to upgrade to Vite 7, test the latest @sentry/vite-plugin in your repo and, if you hit issues, open an issue on the Sentry bundler-plugins repo.
Sources:
- Vite 7 announcement (release notes). [1]
- Sentry docs advising bundler-plugin upgrades (recommendation to upgrade bundler plugins to avoid SDK version mismatches). [2]
- Sentry JavaScript bundler-plugins repository (official
@sentry/vite-pluginsource / issue tracker). [3]
References:
- Vite 7 announcement — vite.dev blog. [1]
- Sentry docs: “Migrate from 7.x to 8.x” / bundler-plugin upgrade note. [2]
- getsentry/sentry-javascript-bundler-plugins (package and issues for
@sentry/vite-plugin). [3]
🌐 Web query:
vite-plugin-solid Vite 7.3.1 compatibility
💡 Result:
Short answer: vite-plugin-solid does not yet officially support Vite 7 (upgrade to Vite 7 introduced breaking/platform changes). The plugin's README/packaging targets earlier Vite releases and the repository has open issues requesting Vite 7 support. Recommend either stay on Vite 6.x until an updated vite-plugin-solid release, or follow/track the GitHub issue for Vite 7 support and releases.
Sources:
- Vite 7 announcement (breaking changes / requirements). [1]
- vite-plugin-solid README (targets earlier Vite versions / repo info). [2]
- Open GitHub issue requesting Vite 7 support in the vite-plugin-solid repo. [3]
Do not upgrade to Vite 7.3.1 until vite-plugin-solid supports Vite 7.
vite-plugin-solid does not yet officially support Vite 7 and has open GitHub issues requesting Vite 7 support. Upgrading to Vite 7.3.1 will likely break this e2e app. Revert to Vite 6.x or wait for vite-plugin-solid to release Vite 7 support. Additionally, verify Node.js version meets Vite 7's requirement (20.19+ or 22.12+) and test @sentry/vite-plugin compatibility if proceeding later.
🤖 Prompt for AI Agents
In `@e2e/solid-router/sentry-integration/package.json` at line 28, Summary: The PR
updated the package.json dependency "vite" to "^7.3.1" which is incompatible
with vite-plugin-solid; revert to Vite 6.x to avoid breaking the e2e app. Fix:
in package.json restore the "vite" entry back to a Vite 6.x range compatible
with vite-plugin-solid (e.g., "^6.x"), ensure you do not change other deps, run
your package manager to reinstall, and run the e2e tests; if you plan to upgrade
later, wait for vite-plugin-solid Vite 7 support, verify Node.js meets Vite 7
requirements (20.19+ or 22.12+), and test `@sentry/vite-plugin` compatibility
before bumping.
| "solid-js": "^1.9.10", | ||
| "tailwind-merge": "^2.6.0", | ||
| "vite": "^7.1.7", | ||
| "vite": "^7.3.1", |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
cat -n e2e/solid-start/query-integration/package.jsonRepository: TanStack/router
Length of output: 174
🌐 Web query:
Vite 7.3.1 release notes breaking changes
💡 Result:
There are no breaking changes listed for Vite 7.3.1 — it's a patch release. See the package CHANGELOG for v7.3.1 and the Vite releases page. [1][2]
Sources:
[1] Vite changelog (v7.3.1 package CHANGELOG). [GitHub]. (github.com)
[2] Vite releases / release notes (Vite 7 blog and releases). (vite.dev)
Citations:
- 1: https://github.com/vitejs/vite/blob/v7.3.1/packages/vite/CHANGELOG.md
- 2: https://vite.dev/blog/announcing-vite7?utm_source=openai
🌐 Web query:
vite-plugin-solid compatibility Vite 7.3.1
💡 Result:
Short answer: Not officially confirmed. Vite 7 is a breaking major release (June 24, 2025) and the vite-plugin-solid repository has an open request to add explicit Vite 7 support — there isn't a published release that states compatibility with Vite 7.3.1. [1][2]
Recommendation: test your project in a branch (or use a container/CI) before upgrading; follow the vite-plugin-solid issue requesting Vite 7 support and the plugin repo for a dedicated release/PR. [2]
Sources:
- Vite 7 announcement. [1]
- vite-plugin-solid repository / open issue tracking Vite 7 support. [2]
🌐 Web query:
@tailwindcss/vite 4.1.18 Vite 7 compatibility
💡 Result:
Short answer: No — @tailwindcss/vite 4.1.18 declares a peerDependency of vite "^5.2.0 || ^6", so it is not officially compatible with Vite 7; users reported install errors and opened issues. [1][2][3]
Options:
- Downgrade to Vite 6 (or use a project scaffold that installs Vite 6). [3]
- Install anyway using npm/yarn flags (npm --legacy-peer-deps or npm install --force / equivalent pnpm/yarn options) — works but bypasses peer-dep checks and may surface runtime issues. [1][2]
- Wait for an updated
@tailwindcss/viterelease that adds Vite 7 to its peerDependencies (watch Tailwind’s repo/Changelog). [2][3]
Sources:
- Vite GitHub issue reporting incompatibility. [turn0search0]
- Tailwind CSS repo issue about Vite 7 support. [turn0search4]
- Tailwind docs and current plugin release listings. [turn0search5][turn0search7]
Revert Vite 7.3.1 — incompatible with current plugins.
Vite 7.3.1 itself is a safe patch release, but @tailwindcss/vite 4.1.18 explicitly declares peerDependency as "^5.2.0 || ^6" and is not compatible with Vite 7. Additionally, vite-plugin-solid does not yet have an official release supporting Vite 7. Downgrade back to Vite 6 or wait for updated plugin releases before upgrading.
🤖 Prompt for AI Agents
In `@e2e/solid-start/query-integration/package.json` at line 23, Restore the Vite
dependency to a Vite 6-compatible version instead of "vite": "^7.3.1" in
package.json; update the "vite" entry back to the previous 6.x constraint (e.g.,
"^6.0.0" or the project's prior pinned 6.x version) so it matches peerDependency
requirements of `@tailwindcss/vite` and compatibility expectations of
vite-plugin-solid.
| "@vitejs/plugin-vue-jsx": "^4.1.2", | ||
| "typescript": "~5.8.3", | ||
| "vite": "^7.1.7", | ||
| "vite": "^7.3.1", |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
cat -n e2e/vue-router/basic-vue-query/package.jsonRepository: TanStack/router
Length of output: 174
🏁 Script executed:
# Find CI configuration files to check Node version
fd -t f -e yml -e yaml -e json | grep -E "(ci|workflow|github|action)" | head -20Repository: TanStack/router
Length of output: 174
🌐 Web query:
Vite 7.3.1 release notes breaking changes
💡 Result:
There are no breaking changes listed for v7.3.1 — it's a patch release (bugfixes/backports). See the package changelog/release entry for details. [1][2][3]
Sources:
[1] Vite v7.3.1 CHANGELOG (packages/vite).
[2] Vite Releases / changelog overview.
[3] vite@7.3.1 package.json (engines & metadata).
🌐 Web query:
@vitejs/plugin-vue 5.2.3 compatibility Vite 7.3.1
💡 Result:
Short answer: No — @vitejs/plugin-vue@5.2.3 declares peerDependency "vite": "^5.0.0 || ^6.0.0", so it does not officially support Vite 7.x (e.g. 7.3.1). [1]
If you need Vite 7.x, upgrade @vitejs/plugin-vue to the v6+ release (latest v6.x). [2]
Sources:
@vitejs/plugin-vuev5.2.3 package.json (peerDependencies: "vite": "^5.0.0 || ^6.0.0"). [1]- npm / package listing showing current v6.x releases. [2]
🌐 Web query:
@vitejs/plugin-vue-jsx 4.1.2 Vite 7.3 compatibility
💡 Result:
Short answer: No — @vitejs/plugin-vue-jsx 4.1.2 does not declare compatibility with Vite 7.x. The 4.x releases list Vite ^5 || ^6 as peer dependencies, while support for Vite ^7 appears in the 5.x plugin releases. [1][2]
Recommendations:
- Upgrade
@vitejs/plugin-vue-jsxto a 5.x release (which adds "vite: ^5 || ^6 || ^7" peer support). [3] - Or keep Vite at a 6.x (or 5.x) version if you must stay on plugin 4.x. [1]
Sources:
- package-lock / node_modules entries showing plugin-vue-jsx (4.x) peerDependencies: "vite": "^5.0.0 || ^6.0.0". [1]
- project lock showing
@vitejs/plugin-vue-jsx@4.1.2 used with vite 6.x. [2] - later plugin release (5.x) showing peerDependencies updated to include Vite ^7.0.0. [3]
Vite 7.3.1 is incompatible with @vitejs/plugin-vue@5.2.3 and @vitejs/plugin-vue-jsx@4.1.2.
Both plugins declare peerDependencies limited to vite: ^5.0.0 || ^6.0.0 and do not officially support Vite 7.x. Either revert Vite to 6.x or upgrade the plugins to versions supporting Vite 7 (e.g., @vitejs/plugin-vue@6.x and @vitejs/plugin-vue-jsx@5.x).
🤖 Prompt for AI Agents
In `@e2e/vue-router/basic-vue-query/package.json` at line 29, package.json
currently pins Vite to "^7.3.1" which is incompatible with
`@vitejs/plugin-vue`@5.2.3 and `@vitejs/plugin-vue-jsx`@4.1.2; update package.json
by either downgrading the "vite" entry to a 6.x range (e.g., "^6.0.0") or
upgrade the plugins to versions that support Vite 7 (e.g., set
`@vitejs/plugin-vue` to 6.x and `@vitejs/plugin-vue-jsx` to 5.x) so peerDependencies
align; adjust the dependency lines for "vite", "@vitejs/plugin-vue", and
"@vitejs/plugin-vue-jsx" in package.json and run install to verify no peer
dependency warnings.
| "@vitejs/plugin-vue-jsx": "^4.1.2", | ||
| "typescript": "~5.8.3", | ||
| "vite": "^7.1.7", | ||
| "vite": "^7.3.1", |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
cat -n e2e/vue-router/generator-cli-only/package.jsonRepository: TanStack/router
Length of output: 174
🌐 Web query:
Vite 7.3.1 release notes breaking changes compatibility
💡 Result:
Short answer: v7.3.1 is a patch release (bugfixes/QoL) for the v7 line and does not introduce new breaking changes to Vite itself — it’s a semver patch compatible with Vite 7. Plugins that still declare strict peerDependencies for older Vite ranges (e.g. @tailwindcss/vite requiring ^5 || ^6) can cause install-time conflicts when moving to Vite 7. [1][2][3]
Sources:
- Dependabot / release note pointing to v7.3.1 changelog. [1]
- Vite repository CHANGELOG (v7.3.1 package changelog). [2]
- Example ecosystem incompatibility issue (plugin peerDependency blocking Vite 7 installs). [3]
🌐 Web query:
@vitejs/plugin-vue 5.2.3 Vite 7.3.1 compatibility
💡 Result:
Short answer: Not officially compatible. @vitejs/plugin-vue 5.2.3 (5.x) declares peer dependency only for Vite 5/6 (e.g. package.json for 5.x shows "vite": "^5.0.0 || ^6.0.0"), so installing it into a project using Vite 7.3.1 will produce a peer-dependency conflict unless you force/ignore it. [1][2]
What to do:
- Best: use a plugin release that explicitly lists support for Vite ^7 (wait for or upgrade to a plugin version that adds Vite 7 in its peerDependencies).
- Workaround (not recommended for long-term): install with npm --legacy-peer-deps or --force / use a package-manager override to bypass the peer-dep check (may cause runtime/breaking issues). [2][3]
Sources:
@vitejs/plugin-vuepackage.json (5.x) — peerDependencies includes vite "^5.0.0 || ^6.0.0". [1]- Examples/discussions of peer-dependency conflicts when plugins expect ^5/6 and Vite 7 is used. [2][3]
References:
[1] @vitejs/plugin-vue (package.json, 5.x).
[2] Vite GitHub issues / community discussions about peer-dep conflicts with Vite 7.
[3] Stack Overflow discussion on plugin-vue / vite version incompatibilities.
🌐 Web query:
@vitejs/plugin-vue-jsx 4.1.2 Vite 7.3.1 compatibility
💡 Result:
Short answer: No — @vitejs/plugin-vue-jsx@4.1.2 is not compatible with Vite 7.3.1. Versions in the v4.x line expect older Vite ranges; use a plugin v5+ release whose peerDependencies include Vite 7 (e.g. v5.x / 5.1.x). [1][2]
Sources:
- example pnpm lock entries showing
@vitejs/plugin-vue-jsx4.x used with Vite 6 (implying v4 targets older Vite). [1] - package/lock entries and package metadata showing
@vitejs/plugin-vue-jsxv5 releases advertise peer support for Vite 5/6/7; latest v5.x is recommended. [2]
If you want, I can look up the exact minimal @vitejs/plugin-vue-jsx version that declares a peerDependency range including ^7.0.0 and give the upgrade command.
🌐 Web query:
@vitejs/plugin-vue latest version Vite 7 support
💡 Result:
Short answer: @vitejs/plugin-vue latest stable is v6.x (current patch v6.0.3) and it supports Vite 7 (v6 even adds Vite 8 support). [1][2][3]
Sources:
@vitejs/plugin-vuev6.0.3 release notes (adds Vite 8 support). [1]- Yarn / npm package listing for
@vitejs/plugin-vueshowing v6.0.3 as latest. [2] - Vite 7 announcement (Vite 7 released). [3]
Upgrade Vue plugins before bumping Vite to 7.3.1.
@vitejs/plugin-vue 5.2.3 only declares peer support for Vite ^5 || ^6, and @vitejs/plugin-vue-jsx 4.1.2 targets older Vite versions. Updating Vite to 7.3.1 will cause peer-dependency conflicts with these plugins and may require --legacy-peer-deps as a workaround (not recommended).
Upgrade to:
@vitejs/plugin-vueto v6.x (latest v6.0.3 supports Vite 7+)@vitejs/plugin-vue-jsxto v5.x (supports Vite 7+)
🤖 Prompt for AI Agents
In `@e2e/vue-router/generator-cli-only/package.json` at line 28, The package.json
currently upgrades the vite dependency to "vite": "^7.3.1" but the Vue plugins
are still on incompatible major versions; update `@vitejs/plugin-vue` to a 6.x
release (e.g., v6.0.3) and `@vitejs/plugin-vue-jsx` to a 5.x release so they
declare peer support for Vite 7+, then update the package.json dependency
entries for "@vitejs/plugin-vue" and "@vitejs/plugin-vue-jsx", regenerate the
lockfile (npm/yarn/pnpm install) and run the test/build step to verify no
peer-dependency conflicts remain.
| "@tanstack/solid-router-devtools": "^1.151.2", | ||
| "tailwindcss": "4.1.18", | ||
| "vite": "^7.1.7", | ||
| "vite": "^7.3.1", |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
cat -n "examples/solid/router-monorepo-solid-query/packages/app/package.json"Repository: TanStack/router
Length of output: 174
🏁 Script executed:
# Check the workspace structure
find examples/solid/router-monorepo-solid-query/packages -name "package.json" -type f | head -10Repository: TanStack/router
Length of output: 174
🏁 Script executed:
# Check if there are any internal dependencies that should use workspace:* protocol
cat -n "examples/solid/router-monorepo-solid-query/package.json"Repository: TanStack/router
Length of output: 174
🌐 Web query:
Vite 7.3.1 compatibility vite-plugin-solid @tailwindcss/vite``
💡 Result:
Short answer:
@tailwindcss/vite: compatible with Vite 7 starting in@tailwindcss/vitev4.1.11+ (older 4.1.10 declares peer vite "^5.2.0 || ^6"). [1][2]- vite-plugin-solid: no official announcement of Vite 7-specific support in the plugin repo; there are open issues requesting Vite 7 support — test with the latest vite-plugin-solid and pin/override if you hit peer errors or stay on Vite 6 until the plugin explicitly documents Vite 7 support. [3][4]
Sources:
- Tailwind docs (Vite guide). [turn0search2] — confirms use of
@tailwindcss/viteand install instructions. - Tailwind GitHub issues / community notes about Vite 7 peer-dep and v4.1.11 adding Vite 7 support. [turn0search5][turn1search3]
- solidjs/vite-plugin-solid repo (issues requesting Vite 7 support). [turn1search7]
- npm / package pages for vite-plugin-solid (no Vite‑7 compatibility release notes). [turn3search8]
If you want, I can check your project’s package.json and suggest exact versions or show how to add an npm override (or package-lock/pnpm override) to work around peer dependency checks.
🌐 Web query:
vite-plugin-solid 2.11.10 requirements Vite version
💡 Result:
vite-plugin-solid 2.11.10 is compatible with Vite (adds Vite 6 compat in 2.11.0 and Vite 7 support in 2.11.8), i.e. it supports Vite v3–v7. [1][2]
Sources:
- changelog / release notes (2.11.8 added Vite 7 support; 2.11.0/2.11.1 added/fixed Vite 6 compat). [1]
- package README / requirements. [2]
🌐 Web query:
@tailwindcss/vite 4.1.18 Vite 7 compatibility
💡 Result:
Short answer: Not officially compatible. @tailwindcss/vite 4.1.18 (4.1.x) declares a peerDependency of "vite": "^5.2.0 || ^6", so it will produce a peer-dependency conflict with Vite 7 and is not officially supported. [1][2]
Options:
- Downgrade your project to Vite 6 (recommended for stability). [1][4]
- Install anyway using npm/yarn overrides or with --force / --legacy-peer-deps (risky — may break runtime behavior). [0][1]
- Skip the plugin and use Tailwind via PostCSS (manual setup) until an updated plugin release adds Vite 7 support. [4]
Sources:
- Vite GitHub issue reporting the peerDependency conflict. [1]
- Tailwind Vite install docs (plugin usage). [4]
- Community writeups describing the conflict and workarounds. [0]
If you want, I can: (a) show the exact peerDependency lines from package.json for 4.1.18, (b) give the exact npm override or package.json snippet to force-accept Vite 7, or (c) walk through a PostCSS-only Tailwind setup for Vite 7.
@tailwindcss/vite 4.1.18 is incompatible with Vite 7.3.1.
The @tailwindcss/vite v4.1.18 package declares a peer dependency of "vite": "^5.2.0 || ^6", which conflicts with Vite 7.3.1. This will cause installation failures or peer dependency warnings.
Options:
- Downgrade Vite to 6.x
- Upgrade
@tailwindcss/viteto a version that supports Vite 7
Note: vite-plugin-solid 2.11.10 is compatible with Vite 7.
🤖 Prompt for AI Agents
In `@examples/solid/router-monorepo-solid-query/packages/app/package.json` at line
22, The package.json currently pins "vite": "^7.3.1" which is incompatible with
the installed "@tailwindcss/vite" v4.1.18 peer dependency; update package.json
to resolve the peer conflict by either downgrading the "vite" version to a 6.x
range (e.g., "^6.0.0") or upgrading the "@tailwindcss/vite" dependency to a
release that explicitly supports Vite 7, ensuring the change is applied to the
"vite" and/or "@tailwindcss/vite" entries so npm/yarn no longer reports a peer
dependency mismatch.
| "combinate": "^1.1.11", | ||
| "typescript": "^5.7.2", | ||
| "vite": "^7.1.7", | ||
| "vite": "^7.3.1", |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
cat examples/solid/start-counter/package.jsonRepository: TanStack/router
Length of output: 174
🌐 Web query:
Vite 7.3.1 release notes breaking changes compatibility
💡 Result:
Short answer: v7.3.1 is a patch release (no breaking changes). It adds a small feature (optimizeDeps.ignoreOutdatedRequests) and otherwise follows Vite 7 compatibility requirements (Node >=20.19 or 22.12, ESM-only distribution, the Vite 7 browser-target changes). Sources: Vite 7 announcement and the v7.3.1 changelog. [1][2]
Sources
- Vite 7 announcement (Node/browser targets, ESM notes). [1]
- Vite v7.3.1 CHANGELOG (feature: optimizeDeps.ignoreOutdatedRequests). [2]
🌐 Web query:
vite-plugin-solid 2.11.10 vite 7 compatibility
💡 Result:
Yes — vite-plugin-solid v2.11.10 is compatible with Vite 7. The plugin added Vite 7 support in the 2.11.x series (2.11.8) and 2.11.10 contains further Vite 6+/SSR fixes. [1][2]
Sources:
- vite-plugin-solid changelog (2.11.x). [1]
- vite-plugin-solid repository README / releases. [2]
🌐 Web query:
vite-tsconfig-paths 5.1.4 vite 7 compatibility
💡 Result:
Short answer: unknown — v5.1.4 (released Dec 6, 2024) predates Vite 7 and does not explicitly claim Vite 7 support; v6 (beta/ongoing) contains newer changes that target more recent Vite behavior. I recommend upgrading to the v6 releases (or testing v5.1.4 in your project) if you need guaranteed compatibility with Vite 7. [1][2]
Sources:
- vite-tsconfig-paths releases (v5.1.4 date + v6 notes). [1]
- vite-tsconfig-paths README / repo (notes about v5→ESM and v6 features). [2]
References:
[1] https://github.com/aleclarson/vite-tsconfig-paths/releases — v5.1.4 (2024‑12‑06) and v6 beta notes.
[2] https://github.com/aleclarson/vite-tsconfig-paths — README (v5/v6 notes).
vite-tsconfig-paths 5.1.4 may lack Vite 7 compatibility; consider upgrading to v6.
Vite 7.3.1 is a safe patch release with no breaking changes. vite-plugin-solid 2.11.10 is confirmed compatible with Vite 7. However, vite-tsconfig-paths 5.1.4 predates Vite 7 and does not explicitly claim Vite 7 support; v6 is recommended for guaranteed compatibility. Either upgrade vite-tsconfig-paths to v6 or verify that v5.1.4 works correctly with Vite 7.3.1 in your project.
🤖 Prompt for AI Agents
In `@examples/solid/start-counter/package.json` at line 26, Update the
vite-tsconfig-paths dependency to a Vite 7–compatible release (upgrade from
"vite-tsconfig-paths" v5.1.4 to v6.x) in package.json so it explicitly supports
Vite 7. Alternatively, if you choose not to upgrade, run a compatibility test
with the current "vite-tsconfig-paths" version against Vite 7.3.1 and document
the result; prefer changing the dependency entry in package.json to
"vite-tsconfig-paths": "^6.0.0" to ensure guaranteed compatibility with vite and
vite-plugin-solid.
| "tailwindcss": "^4.1.18", | ||
| "typescript": "^5.7.2", | ||
| "vite": "^7.1.7", | ||
| "vite": "^7.3.1", |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
cat -n examples/solid/start-supabase-basic/package.jsonRepository: TanStack/router
Length of output: 174
🌐 Web query:
Vite 7.3.1 compatibility vite-plugin-solid
💡 Result:
Short answer: Partial — vite-plugin-solid does not yet have an official released version fully tested for Vite 7. Vite 7 is released (June 24, 2025) and the Vite team lists 7.x as current; the vite-plugin-solid repo shows open issues/PRs tracking Vite 7 support, and some registries mention 7.x compatibility but the plugin’s stable npm releases are primarily for earlier Vite majors. Check the plugin’s GitHub issues/PRs or use the plugin’s main branch for the latest Vite‑7 fixes before upgrading. [1][2][3]
Sources:
- Vite 7 announcement. [1]
- solidjs/vite-plugin-solid repository (issues and README). [2]
- npm/tessl registry notes and compatibility mentions. [3]
🌐 Web query:
@tailwindcss/vite 4.1.18 Vite 7.3 compatibility
💡 Result:
Short answer: Not officially compatible. @tailwindcss/vite v4.1.x declares a peer dependency restricting Vite to ^5.2.0 || ^6, so installing it into a Vite 7.3 project will trigger peer-dependency errors (others have reported the same). [1][2]
Workarounds:
- Downgrade Vite to a 6.x series (recommended until the plugin adds Vite 7 support). [1][3]
- Force install / use npm's overrides or --force / --legacy-peer-deps (may work but can cause runtime or subtle incompatibilities). [3]
References:
- Vite GitHub issue discussing the peer-dep incompatibility. [1]
- Tailwind docs for the Vite plugin (installation instructions). [2]
- Community writeup with workaround options. [3]
If you want, I can check the exact peerDependencies in @tailwindcss/vite@4.1.18 (package.json) and search whether a newer plugin release adds explicit Vite 7 support.
🌐 Web query:
Vite 7.3.1 release notes breaking changes
💡 Result:
Short answer: There are no breaking changes listed for Vite v7.3.1 — it's a patch; see the v7.3.1 package changelog. [1][2]
Sources:
- Vite v7.3.1 package CHANGELOG (referenced in the v7.3.1 tag). [1]
- Source snapshot / diff referencing packages/vite/CHANGELOG.md for v7.3.1. [2]
Vite 7.3.1 is incompatible with @tailwindcss/vite 4.1.18 — critical blocker (Line 28).
@tailwindcss/vite 4.1.18 declares a peerDependency limiting Vite to ^5.2.0 || ^6, which excludes Vite 7.3.1. This will cause peer-dependency errors and install failures. Additionally, vite-plugin-solid lacks stable Vite 7 support with open tracking issues.
Either downgrade Vite to 6.x or upgrade @tailwindcss/vite and vite-plugin-solid to versions with Vite 7 support.
🤖 Prompt for AI Agents
In `@examples/solid/start-supabase-basic/package.json` at line 28, The
package.json currently pins "vite": "^7.3.1" which is incompatible with
`@tailwindcss/vite`@4.1.18 (peerDependency ^5.2.0 || ^6) and with
vite-plugin-solid’s unstable Vite 7 support; either change the Vite entry in
package.json to a 6.x range (e.g., "vite": "^6.0.0") to match
`@tailwindcss/vite`@4.1.18, or instead update the plugin dependencies
(`@tailwindcss/vite` and vite-plugin-solid) to versions that explicitly support
Vite 7; locate the "vite" field in package.json and make one consistent change
(downgrade Vite to ^6.x or upgrade the two plugins) and then run npm/yarn
install to verify peerDependency resolution.
| "vite-plugin-solid": "^2.11.10", | ||
| "typescript": "^5.7.2", | ||
| "vite": "^7.1.7" | ||
| "vite": "^7.3.1" |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
cat examples/solid/view-transitions/package.jsonRepository: TanStack/router
Length of output: 174
🌐 Web query:
Vite 7.3.1 release notes breaking changes
💡 Result:
Do you mean Vite version 7.3.1 (the patch release)? If so I can fetch the official release/changelog and list any breaking changes — confirm and I’ll look it up.
🌐 Web query:
vite-plugin-solid Vite 7 compatibility
💡 Result:
Short answer: Not yet officially. Vite 7 was released June 24, 2025, but the solidjs/vite-plugin-solid repository still has open issues requesting Vite 7 support (no released version announcing Vite‑7 compatibility). [1][2]
Sources:
- Vite 7 announcement (June 24, 2025). [1]
- solidjs/vite-plugin-solid GitHub issues (open request(s) for Vite 7 support). [2]
Revert Vite bump — vite-plugin-solid does not yet support Vite 7.
Vite 7.3.1 is incompatible with vite-plugin-solid, which has no released version supporting Vite 7. Downgrade Vite to the latest 6.x version or wait for vite-plugin-solid to release Vite 7 compatibility.
🤖 Prompt for AI Agents
In `@examples/solid/view-transitions/package.json` at line 24, Revert the Vite
version bump in package.json: change the "vite" dependency back to a Vite 6.x
release compatible with vite-plugin-solid (use the latest 6.x semver range, e.g.
^6.x) and update lockfiles (run npm/yarn install) so the project uses a Vite
6-compatible install; ensure vite-plugin-solid remains at a version that
supports Vite 6.
| "devDependencies": { | ||
| "solid-js": "^1.9.10", | ||
| "vite": "^7.1.7", | ||
| "vite": "^7.3.1", |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
cat packages/router-devtools-core/package.json | head -80Repository: TanStack/router
Length of output: 174
🌐 Web query:
Vite 7.3.1 minimum Node.js version requirements
💡 Result:
Vite 7 (including 7.3.1) requires Node.js 20.19+ or 22.12+. [1][2]
Sources:
- Vite 7 announcement (Node.js 20.19+, 22.12+). [1]
- Vite migration guide / Node.js support note. [2]
🌐 Web query:
vite-plugin-solid 2.11.10 compatibility with Vite 7 or later
💡 Result:
Short answer: Yes. Support for Vite 7 was added in vite-plugin-solid 2.11.8 (peerDeps) and 2.11.10 includes subsequent fixes (SSR/Vite 6+/7+ related), so 2.11.10 is intended to be compatible with Vite 7. [1][2]
Sources:
- Changelog showing "add support for vite 7 in peerDeps" and Vite‑7 fixes. [1]
- Package README/repo (plugin releases/notes). [2]
🌐 Web query:
site:github.com TanStack/router packages/router-devtools-core/package.json engines.node
💡 Result:
The package.json for @tanstack/router-devtools-core specifies "engines.node": ">=12". [1][2]
Sources:
- pnpm-lock snippet showing
@tanstack/router-devtools-coreengines: { node: '>=12' }. [1] - package.json for related TanStack router package on UNPKG showing "engines": { "node": ">=12" }. [2]
Update engines.node constraint to match Vite 7.3.1 requirements.
Vite 7.3.1 requires Node.js 20.19+ or 22.12+, but this package declares engines.node: ">=12". The constraint must be updated to align with the minimum Node version required by Vite 7.3.1 (e.g., ">=20.19"). vite-plugin-solid 2.11.10 is compatible with Vite 7.3.1, so that dependency is fine.
🤖 Prompt for AI Agents
In `@packages/router-devtools-core/package.json` at line 71, Update the
package.json engines.node constraint to match Vite 7.3.1's minimum Node version
requirement by replacing the current "engines.node" value with a more
restrictive constraint such as ">=20.19" (or ">=20.19 || >=22.12" if you prefer
to express both lines), ensuring it aligns with the declared dependency "vite":
"^7.3.1"; leave vite-plugin-solid as-is since it's compatible.
There was a problem hiding this comment.
Actionable comments posted: 6
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (11)
examples/react/basic-file-based/package.json (1)
23-27: Upgrade@vitejs/plugin-reactto v5+ for Vite 7.3.1 compatibility.
@vitejs/plugin-react4.3.4 does not support Vite 7.x (its peerDependencies only cover up to Vite 6). This version bump will cause peer-dependency conflicts. Upgrade@vitejs/plugin-reactto v5 or later, which includes Vite 7 in its peerDependencies range. Also confirm the repo's Node.js target supports Node.js 20.19+ or 22.12+, which are now required by Vite 7.3.1.examples/react/router-monorepo-react-query/packages/app/package.json (1)
19-26: @vitejs/plugin-react@4.3.4 is not compatible with Vite 7.3.1 — this combination will fail.Vite 7.3.1 requires Node.js 20.19+ or 22.12+ (Node 18 support removed), and
@vitejs/plugin-react@4.3.4 declares peerDependencies only up through Vite 6. Either upgrade@vitejs/plugin-reactto a version that supports Vite 7, or pin Vite to a version ≤6.examples/react/router-monorepo-simple/packages/router/package.json (1)
10-24: Use workspace: for internal@tanstackdeps.*Line 11-13 should use the workspace protocol to ensure local linking and avoid version drift.
♻️ Proposed fix
- "@tanstack/history": "^1.151.1", - "@tanstack/react-router": "^1.151.2", - "@tanstack/router-plugin": "^1.151.2", + "@tanstack/history": "workspace:*", + "@tanstack/react-router": "workspace:*", + "@tanstack/router-plugin": "workspace:*",As per coding guidelines, internal dependencies must use
workspace:*.examples/solid/start-bun/package.json (1)
15-38: Use workspace: for internal@tanstackdeps.*Line 17-23 and Line 28 should use workspace protocol.
♻️ Proposed fix
- "@tanstack/solid-devtools": "^0.7.0", - "@tanstack/solid-router": "^1.151.2", - "@tanstack/solid-router-devtools": "^1.151.2", - "@tanstack/solid-router-ssr-query": "^1.151.2", - "@tanstack/solid-start": "^1.151.2", - "@tanstack/router-plugin": "^1.151.2", + "@tanstack/solid-devtools": "workspace:*", + "@tanstack/solid-router": "workspace:*", + "@tanstack/solid-router-devtools": "workspace:*", + "@tanstack/solid-router-ssr-query": "workspace:*", + "@tanstack/solid-start": "workspace:*", + "@tanstack/router-plugin": "workspace:*", @@ - "@tanstack/eslint-config": "^0.3.2", + "@tanstack/eslint-config": "workspace:*",As per coding guidelines, internal dependencies must use
workspace:*.e2e/react-start/basic-tsr-config/package.json (1)
13-22: Standardize internal deps to workspace:*.Line 14-16 and Line 21 should use
workspace:*(notworkspace:^) per repo policy.♻️ Proposed fix
- "@tanstack/react-router": "workspace:^", - "@tanstack/react-start": "workspace:^", + "@tanstack/react-router": "workspace:*", + "@tanstack/react-start": "workspace:*", @@ - "@tanstack/router-e2e-utils": "workspace:^", + "@tanstack/router-e2e-utils": "workspace:*",As per coding guidelines, internal dependencies must use
workspace:*.examples/solid/large-file-based/package.json (1)
13-27: Use workspace: for internal@tanstackdeps.*Line 15-18 should use the workspace protocol.
♻️ Proposed fix
- "@tanstack/solid-query": "^5.90.9", - "@tanstack/solid-router": "^1.151.2", - "@tanstack/solid-router-devtools": "^1.151.2", - "@tanstack/router-plugin": "^1.151.2", + "@tanstack/solid-query": "workspace:*", + "@tanstack/solid-router": "workspace:*", + "@tanstack/solid-router-devtools": "workspace:*", + "@tanstack/router-plugin": "workspace:*",As per coding guidelines, internal dependencies must use
workspace:*.examples/solid/basic-file-based/package.json (1)
11-24: Use workspace: for internal@tanstackdeps.*Line 13-14 and Line 21 should use the workspace protocol.
♻️ Proposed fix
- "@tanstack/solid-router": "^1.151.2", - "@tanstack/solid-router-devtools": "^1.151.2", + "@tanstack/solid-router": "workspace:*", + "@tanstack/solid-router-devtools": "workspace:*", @@ - "@tanstack/router-plugin": "^1.151.2", + "@tanstack/router-plugin": "workspace:*",As per coding guidelines, internal dependencies must use
workspace:*.e2e/vue-start/css-modules/package.json (1)
22-30: Upgrade@vitejs/plugin-vue-jsxto support Vite 7.3.1.
@vitejs/plugin-vue-jsx4.1.2 declares peer support only for Vite ^5.0.0 || ^6.0.0 and is incompatible with Vite 7.3.1. Upgrade the plugin to a version that supports Vite 7.x, or downgrade Vite. vite-tsconfig-paths 5.1.4 is compatible (accepts any Vite version).e2e/vue-start/scroll-restoration/package.json (1)
15-18: Useworkspace:*for internal dependencies.
workspace:^should beworkspace:*to follow the workspace protocol convention across this repo.🔧 Suggested change
- "@tanstack/vue-router": "workspace:^", - "@tanstack/vue-router-devtools": "workspace:^", - "@tanstack/vue-start": "workspace:^", - "@tanstack/zod-adapter": "workspace:^", + "@tanstack/vue-router": "workspace:*", + "@tanstack/vue-router-devtools": "workspace:*", + "@tanstack/vue-start": "workspace:*", + "@tanstack/zod-adapter": "workspace:*",As per coding guidelines, internal dependencies must use
workspace:*.e2e/react-start/website/package.json (1)
15-17: Useworkspace:*for internal dependencies.🔧 Suggested change
- "@tanstack/react-router": "workspace:^", - "@tanstack/react-router-devtools": "workspace:^", - "@tanstack/react-start": "workspace:^", + "@tanstack/react-router": "workspace:*", + "@tanstack/react-router-devtools": "workspace:*", + "@tanstack/react-start": "workspace:*",As per coding guidelines, internal dependencies must use
workspace:*.e2e/react-start/virtual-routes/package.json (1)
15-18: Useworkspace:*for internal dependencies.🔧 Suggested change
- "@tanstack/react-router": "workspace:^", - "@tanstack/react-router-devtools": "workspace:^", - "@tanstack/react-start": "workspace:^", - "@tanstack/virtual-file-routes": "workspace:^", + "@tanstack/react-router": "workspace:*", + "@tanstack/react-router-devtools": "workspace:*", + "@tanstack/react-start": "workspace:*", + "@tanstack/virtual-file-routes": "workspace:*",As per coding guidelines, internal dependencies must use
workspace:*.
🤖 Fix all issues with AI agents
In `@e2e/react-router/basic-file-based/package.json`:
- Line 33: The package.json currently pins "vite": "^7.3.1" which is
incompatible with the installed "@vitejs/plugin-react" peer range; update the
dependency pair so they match: either upgrade "@vitejs/plugin-react" to a
release that supports Vite 7.x or change "vite" to a compatible ^6.x range; edit
the package.json entries for "vite" and/or "@vitejs/plugin-react" (referencing
those exact keys) and run install to ensure peer versions align and tests pass.
In `@e2e/solid-start/website/package.json`:
- Line 21: The package.json currently lists "vite" in dependencies; move it to
devDependencies to reflect that it's a development tool and to match other e2e
packages. Open the package.json in the e2e/solid-start/website package, remove
the "vite" entry from the "dependencies" object and add the same version string
under the "devDependencies" object, preserving the exact version specifier
("^7.3.1") and JSON formatting.
In `@e2e/vue-router/generator-cli-only/package.json`:
- Line 28: The package.json currently pins "@vitejs/plugin-vue-jsx" to an older
4.x release which is incompatible with the project's "vite": "^7.3.1"; update
the dependency "@vitejs/plugin-vue-jsx" to a 5.x release (e.g., "^5.0.0") in
package.json so its peer dependency range matches Vite 7, then run npm/yarn
install and verify build scripts (look for uses of `@vitejs/plugin-vue-jsx` in any
vite.config.* where the plugin is imported/registered to ensure no API changes
are needed).
In `@e2e/vue-start/basic/package.json`:
- Line 33: Update package.json dependencies: bump `@vitejs/plugin-vue` to a 6.x
(or newer) release that declares compatibility with Vite 7.x so it satisfies the
peer dependency for "vite": "^7.3.1"; also verify and if necessary upgrade
`@vitejs/plugin-vue-jsx` (currently 4.1.2) to a version that supports Vite 7.x,
leaving vite-tsconfig-paths (5.1.4) as-is if compatible; make these changes in
the dependencies/devDependencies entries where "vite", "@vitejs/plugin-vue",
"@vitejs/plugin-vue-jsx", and "vite-tsconfig-paths" are declared and run
npm/yarn install to update lockfile.
In `@examples/solid/start-streaming-data-from-server-functions/package.json`:
- Line 23: The package.json currently pins the dependency "vite": "^7.3.1",
which may not exist on npm and will break installs; update the vite entry in
package.json (the "vite" dependency) to a published version such as "^7.1.4" or
verify and replace with the exact published 7.3.1 if/when it appears on npm,
then run npm install to confirm resolution.
In `@examples/solid/start-tailwind-v4/package.json`:
- Line 25: The package.json currently pins "vite": "^7.3.1" which is
incompatible with the project's plugins (`@tailwindcss/vite` and
vite-plugin-solid) that only declare Vite 5/6 peer deps; change the Vite
dependency back to a compatible 6.x version (e.g., update the "vite" entry to a
6.x semver like "^6.X.Y" or the previous working version) so the peer-dependency
constraints for `@tailwindcss/vite` and vite-plugin-solid are satisfied, or
alternatively hold the Vite bump until those plugins publish Vite 7 support.
♻️ Duplicate comments (12)
examples/react/start-streaming-data-from-server-functions/package.json (1)
26-26: Same Vite bump as elsewhere.Please apply the same Vite 7.3.1 compatibility verification noted earlier.
e2e/react-start/website/package.json (1)
35-35: Same Vite bump as elsewhere.Please apply the same Vite 7.3.1 compatibility verification noted earlier.
examples/react/start-large/package.json (1)
33-33: Same Vite bump as elsewhere.Please apply the same Vite 7.3.1 compatibility verification noted earlier.
examples/solid/start-supabase-basic/package.json (1)
28-28: Same Vite bump as elsewhere.Please apply the same Vite 7.3.1 compatibility verification noted earlier.
e2e/react-start/virtual-routes/package.json (1)
23-23: Same Vite bump as elsewhere.Please apply the same Vite 7.3.1 compatibility verification noted earlier.
examples/solid/router-monorepo-solid-query/packages/app/package.json (1)
22-22: Same Vite bump—verify compatibility.Please ensure this package’s Vite 7.3.1 bump is compatible with existing plugins and scripts.
e2e/react-start/scroll-restoration/package.json (1)
23-23: Vite bump in deps—confirm e2e tooling compatibility.Please verify Vite 7.3.1 works with the current e2e setup and plugins in this package.
e2e/react-start/server-functions/package.json (1)
25-25: Vite bump in deps—confirm e2e tooling compatibility.Please verify Vite 7.3.1 works with the current e2e setup and plugins in this package.
e2e/react-start/csp/package.json (1)
14-19: Same Vite bump as earlier.No additional concerns beyond the Vite 7.3.1 verification already noted.
examples/solid/router-monorepo-simple-lazy/packages/app/package.json (1)
21-26: Same Vite bump as earlier.No additional concerns beyond the Vite 7.3.1 verification already noted.
examples/solid/router-monorepo-simple-lazy/packages/router/package.json (1)
19-22: Same Vite bump as earlier.No additional concerns beyond the Vite 7.3.1 verification already noted.
e2e/vue-router/basic-file-based-sfc/package.json (1)
27-31: Same Vite bump as earlier.No additional concerns beyond the Vite 7.3.1 verification already noted.
🧹 Nitpick comments (1)
packages/router-core/src/utils.ts (1)
476-479: ConfirmisPromiseshould exclude callable thenables.With the
‘object’check, function-thenables no longer pass. If that’s unintentional, consider accepting functions too.Optional adjustment to accept function-thenables
- return Boolean( - value && - typeof value === 'object' && - typeof (value as Promise<T>).then === 'function', - ) + return Boolean( + value && + (typeof value === 'object' || typeof value === 'function') && + typeof (value as Promise<T>).then === 'function', + )
| "@vitejs/plugin-react": "^4.3.4", | ||
| "combinate": "^1.1.11", | ||
| "vite": "^7.1.7" | ||
| "vite": "^7.3.1" |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
cat e2e/react-router/basic-file-based/package.jsonRepository: TanStack/router
Length of output: 174
🌐 Web query:
Vite 7.3.1 release notes breaking changes
💡 Result:
There are no breaking changes listed for Vite v7.3.1 — it’s a patch release (adds an optimizeDeps.ignoreOutdatedRequests option plus fixes). See the v7.3.1 changelog/release note. [1][2]
Sources
- Vite releases (GitHub releases listing). [1]
- packages/vite CHANGELOG.md (v7.3.1). [2]
🌐 Web query:
@vitejs/plugin-react 4.3.4 peer dependency vite version range
💡 Result:
@vitejs/plugin-react@4.3.4 declares Vite as a peer dependency: "vite": "^4.2.0 || ^5.0.0 || ^6.0.0". [1][2]
Sources:
- Release / changelog noting Vite 6 added to peerDependencies. [1]
- npm package listing for
@vitejs/plugin-reactv4.3.4 (peerDependency range shown). [2]
@vitejs/plugin-react 4.3.4 does not support Vite 7.3.1.
The plugin's peer dependency range is "vite": "^4.2.0 || ^5.0.0 || ^6.0.0", which excludes Vite 7.x. Either upgrade @vitejs/plugin-react to a version supporting Vite 7, or downgrade vite to ^6.
🤖 Prompt for AI Agents
In `@e2e/react-router/basic-file-based/package.json` at line 33, The package.json
currently pins "vite": "^7.3.1" which is incompatible with the installed
"@vitejs/plugin-react" peer range; update the dependency pair so they match:
either upgrade "@vitejs/plugin-react" to a release that supports Vite 7.x or
change "vite" to a compatible ^6.x range; edit the package.json entries for
"vite" and/or "@vitejs/plugin-react" (referencing those exact keys) and run
install to ensure peer versions align and tests pass.
| "solid-js": "^1.9.10", | ||
| "tailwind-merge": "^2.6.0", | ||
| "vite": "^7.1.7", | ||
| "vite": "^7.3.1", |
There was a problem hiding this comment.
Vite is listed under dependencies instead of devDependencies.
Vite is typically a development tool and should be in devDependencies. Other e2e packages in this PR (and the codebase) list vite under devDependencies. Consider moving it for consistency.
Suggested fix
Move vite from dependencies to devDependencies:
"dependencies": {
"@tanstack/solid-router": "workspace:^",
"@tanstack/solid-router-devtools": "workspace:^",
"@tanstack/solid-start": "workspace:^",
"redaxios": "^0.5.1",
"solid-js": "^1.9.10",
"tailwind-merge": "^2.6.0",
- "vite": "^7.3.1",
"zod": "^3.24.2"
},
"devDependencies": {
"@playwright/test": "^1.50.1",
"@tailwindcss/vite": "^4.1.18",
"@tanstack/router-e2e-utils": "workspace:^",
"@types/node": "^22.10.2",
"srvx": "^0.10.0",
"tailwindcss": "^4.1.18",
"typescript": "^5.7.2",
+ "vite": "^7.3.1",
"vite-plugin-solid": "^2.11.10",
"vite-tsconfig-paths": "^5.1.4"
}📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| "vite": "^7.3.1", | |
| "dependencies": { | |
| "@tanstack/solid-router": "workspace:^", | |
| "@tanstack/solid-router-devtools": "workspace:^", | |
| "@tanstack/solid-start": "workspace:^", | |
| "redaxios": "^0.5.1", | |
| "solid-js": "^1.9.10", | |
| "tailwind-merge": "^2.6.0", | |
| "zod": "^3.24.2" | |
| }, | |
| "devDependencies": { | |
| "@playwright/test": "^1.50.1", | |
| "@tailwindcss/vite": "^4.1.18", | |
| "@tanstack/router-e2e-utils": "workspace:^", | |
| "@types/node": "^22.10.2", | |
| "srvx": "^0.10.0", | |
| "tailwindcss": "^4.1.18", | |
| "typescript": "^5.7.2", | |
| "vite": "^7.3.1", | |
| "vite-plugin-solid": "^2.11.10", | |
| "vite-tsconfig-paths": "^5.1.4" | |
| } |
🤖 Prompt for AI Agents
In `@e2e/solid-start/website/package.json` at line 21, The package.json currently
lists "vite" in dependencies; move it to devDependencies to reflect that it's a
development tool and to match other e2e packages. Open the package.json in the
e2e/solid-start/website package, remove the "vite" entry from the "dependencies"
object and add the same version string under the "devDependencies" object,
preserving the exact version specifier ("^7.3.1") and JSON formatting.
| "@vitejs/plugin-vue-jsx": "^4.1.2", | ||
| "typescript": "~5.8.3", | ||
| "vite": "^7.1.7", | ||
| "vite": "^7.3.1", |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
cat -n e2e/vue-router/generator-cli-only/package.jsonRepository: TanStack/router
Length of output: 174
🌐 Web query:
Vite 7.3.1 @vitejs/plugin-vue 5.2.3 compatibility release notes
💡 Result:
I can fetch those release notes — do you want a short compatibility summary or the full GitHub/NPM release pages (links)?
🌐 Web query:
Vite 7.3.1 breaking changes @vitejs/plugin-vue5.2.3@vitejs/plugin-vue-jsx 4.1.2 compatibility
💡 Result:
Short answer: @vitejs/plugin-vue@5.2.3 is expected to work with Vite 7.3.1; @vitejs/plugin-vue-jsx@4.1.2 is older and may be incompatible — upgrade the JSX plugin to the current 5.x series to be safe.
Why / sources:
- Vite's plugin ecosystem moved plugin-vue to the 5.x line to follow newer Vite majors; projects have updated to
@vitejs/plugin-vue@5.2.x when using newer Vite versions. [1][2] - Older plugin releases (plugin-vue/plugin-vue-jsx v4.x) declared peer ranges for earlier Vite majors and caused peer-resolution errors when Vite moved to newer majors (reports and guidance in issues/StackOverflow). That same experience applies to the JSX plugin: v4.x was tied to older Vite ranges, while v5.x is the supported line for recent Vite releases. [3][4]
What I recommend (quick steps)
- Inspect the plugin package peerDependencies in your lockfile or on the package registry: e.g. check package.json for
@vitejs/plugin-vue@5.2.3 and@vitejs/plugin-vue-jsx@4.1.2 to confirm their "vite" peer range. (You can open the package.json on the registry or via unpkg/jsdelivr). [2][5] - If plugin-vue-jsx@4.1.2 shows a peer range excluding vite@7, upgrade it: npm install -D
@vitejs/plugin-vue-jsx@latest (5.x). Keep@vitejs/plugin-vueat 5.2.x or update to the latest 5.x as well. [2][4] - Run install and test — if you hit ERESOLVE / peer dependency errors, adjust plugin versions to match Vite's major per the peer ranges. (Community issues document exactly this class of error). [3][4]
References
- Vite breaking/changes and plugin docs (Vite site). [1]
@vitejs/plugin-vuepackage listings / unpkg/npm records showing v5.2.x usage in projects. [2][5]- GitHub/issue reports and StackOverflow showing peer-dependency conflicts when plugins <5 are used with newer Vite majors. [3][4]
If you want, I can fetch the exact peerDependency lines from the two package.json files and paste them here.
Upgrade @vitejs/plugin-vue-jsx to 5.x for Vite 7.3.1 compatibility.
@vitejs/plugin-vue-jsx 4.1.2 is incompatible with Vite 7.x; this version's peer dependencies are constrained to older Vite majors. Upgrade to @vitejs/plugin-vue-jsx@5.x to resolve the incompatibility and align with Vite 7.3.1.
🤖 Prompt for AI Agents
In `@e2e/vue-router/generator-cli-only/package.json` at line 28, The package.json
currently pins "@vitejs/plugin-vue-jsx" to an older 4.x release which is
incompatible with the project's "vite": "^7.3.1"; update the dependency
"@vitejs/plugin-vue-jsx" to a 5.x release (e.g., "^5.0.0") in package.json so
its peer dependency range matches Vite 7, then run npm/yarn install and verify
build scripts (look for uses of `@vitejs/plugin-vue-jsx` in any vite.config.*
where the plugin is imported/registered to ensure no API changes are needed).
| "vue": "^3.5.16", | ||
| "tailwind-merge": "^2.6.0", | ||
| "vite": "^7.1.7", | ||
| "vite": "^7.3.1", |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
cat -n e2e/vue-start/basic/package.jsonRepository: TanStack/router
Length of output: 174
🌐 Web query:
Vite 7.3.1 release notes breaking changes compatibility
💡 Result:
Short answer: v7.3.1 is a patch release (no new broad breaking changes introduced beyond Vite 7). The breaking/compatibility items to watch for are the Vite 7 migration requirements and breaking changes (Node and browser targets, ESM-only distribution, Vitest requirement, some removed legacy APIs) introduced by the Vite 7 major release — you must satisfy those when upgrading to any 7.x release. See official notes below.
Key compatibility / breaking items from Vite 7:
- Node.js minimum: 20.19+ or 22.12+ (Node 18 dropped). [1]
- Vite is distributed ESM-only (CJS consumers may need require(esm) shims). [1]
- Default browser target changed to "baseline-widely-available" (higher minimum browser versions). [1]
- Vitest 3.2+ recommended/required for test environment compatibility. [1]
- Migration guide lists other removals/deprecations (e.g. legacy Sass APIs, some plugin/SSR edges and future changes). Check the Migration guide for specifics. [2]
- v7.3.1 itself is a patch; see the releases/changelog for the exact v7.3.1 changelog link. [3]
Sources:
- Vite 7 announcement / release notes. [1]
- Vite migration guide / breaking changes (Migration from v7). [2]
- Vite releases / GitHub releases (v7.x changelogs). [3]
🌐 Web query:
@vitejs/plugin-vue 5.2.4 compatibility Vite 7.3.1
💡 Result:
No — @vitejs/plugin-vue@5.2.4 declares a peer dependency of vite: ^5.0.0 || ^6.0.0, so it is not compatible with Vite 7.3.1. Upgrade to @vitejs/plugin-vue v6+ (which adds Vite 7 support) or downgrade Vite to a 5.x/6.x release. [1][2]
Sources:
- package deps for
@vitejs/plugin-vue@5.2.4 showing vite: ^5.0.0 || ^6.0.0. [1] @vitejs/plugin-vuepackage.json for v6.x adding vite ^7 support. [2]
🌐 Web query:
vite-tsconfig-paths 5.1.4 Vite 7.3.1 compatibility
💡 Result:
Short answer: yes — vite-tsconfig-paths v5.1.4 is compatible with Vite 7.3.1.
Why: the plugin’s published package allows (or historically allowed) broad Vite versions (peer dependency like "vite": "*" / ">2.0.0-0"), and v5.x is ESM-aligned with Vite’s modern API. If you need the newer on-demand tsconfig loading / projectDiscovery features, upgrade to v6.x (announced in the repo). [1][2][3]
Sources:
- vite-tsconfig-paths README / repo (notes about v5/v6 and ESM). [1]
- package.json (peerDependencies showing broad Vite support). [2]
- release listing showing v5.1.4 (Dec 6, 2024). [3]
Upgrade @vitejs/plugin-vue to v6.x to support Vite 7.3.1.
@vitejs/plugin-vue 5.2.4 declares a peer dependency of vite: ^5.0.0 || ^6.0.0 and is incompatible with Vite 7.3.1. Upgrade to @vitejs/plugin-vue v6+ (or higher) to enable Vite 7 support. Separately, verify that @vitejs/plugin-vue-jsx 4.1.2 also supports Vite 7. vite-tsconfig-paths 5.1.4 is compatible.
🤖 Prompt for AI Agents
In `@e2e/vue-start/basic/package.json` at line 33, Update package.json
dependencies: bump `@vitejs/plugin-vue` to a 6.x (or newer) release that declares
compatibility with Vite 7.x so it satisfies the peer dependency for "vite":
"^7.3.1"; also verify and if necessary upgrade `@vitejs/plugin-vue-jsx` (currently
4.1.2) to a version that supports Vite 7.x, leaving vite-tsconfig-paths (5.1.4)
as-is if compatible; make these changes in the dependencies/devDependencies
entries where "vite", "@vitejs/plugin-vue", "@vitejs/plugin-vue-jsx", and
"vite-tsconfig-paths" are declared and run npm/yarn install to update lockfile.
| "vite-plugin-solid": "^2.11.10", | ||
| "typescript": "^5.7.2", | ||
| "vite": "^7.1.7", | ||
| "vite": "^7.3.1", |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
Vite 7.3.1 release breaking changes changelog
💡 Result:
Vite v7.3.1 is a patch release — there are no breaking changes listed for v7.3.1. See the Vite releases page and the v7.3.1 CHANGELOG on GitHub for details. [1][2]
Sources:
- Vite releases (GitHub releases list). [1]
- vite/packages/vite/CHANGELOG.md (v7.3.1 tag). [2]
🌐 Web query:
latest Vite version 2025
💡 Result:
As of January 18, 2026:
- Latest stable release on npm: vite 7.1.4. [1]
- v8 is available as pre-release/beta on GitHub (e.g. v8.0.0‑beta.5). [2]
- Vite's official blog documents the v6 major announcement (for context on release history). [3]
Sources: [1] npm package page for vite; [2] vitejs/vite GitHub releases; [3] Vite blog announcement.
🏁 Script executed:
cat examples/solid/start-streaming-data-from-server-functions/package.json | grep -A 2 -B 2 '"vite"'Repository: TanStack/router
Length of output: 174
Vite version 7.3.1 may not be available on npm yet.
As of January 18, 2026, the latest stable release on npm is vite 7.1.4. Specifying ^7.3.1 in package.json will cause npm install failures since this version is not yet available on the npm registry. Verify that v7.3.1 has been published to npm before merging, or downgrade to a released version like ^7.1.4.
🤖 Prompt for AI Agents
In `@examples/solid/start-streaming-data-from-server-functions/package.json` at
line 23, The package.json currently pins the dependency "vite": "^7.3.1", which
may not exist on npm and will break installs; update the vite entry in
package.json (the "vite" dependency) to a published version such as "^7.1.4" or
verify and replace with the exact published 7.3.1 if/when it appears on npm,
then run npm install to confirm resolution.
| "tailwindcss": "^4.1.18", | ||
| "typescript": "^5.7.2", | ||
| "vite": "^7.1.7", | ||
| "vite": "^7.3.1", |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
cat examples/solid/start-tailwind-v4/package.jsonRepository: TanStack/router
Length of output: 174
🏁 Script executed:
cat package.json | head -30Repository: TanStack/router
Length of output: 174
🌐 Web query:
Vite 7.3.1 release notes breaking changes
💡 Result:
Vite v7.3.1 is a patch release and the CHANGELOG/release notes do not list any breaking changes. See the v7.3.1 changelog on the Vite repo. (github.com)
Citations:
🌐 Web query:
@tailwindcss/vite Vite 7.3.1 compatibility
💡 Result:
Short answer: As of the Vite 7 release (June 24, 2025) the official @tailwindcss/vite package still declares a peer dependency of "vite": "^5.2.0 || ^6", so installing it in a Vite 7 project triggers a peer-dependency warning/error (i.e., not officially updated for Vite 7 yet). You can work around it with --force / --legacy-peer-deps or stick to Vite 6 until the plugin updates. [1][2][3]
Sources:
- Tailwind issue tracking Vite 7 peer-warning for
@tailwindcss/vite. [1] - Vite repository issue reporting the peer-dependency incompatibility. [2]
- Vite 7 announcement (release date / context). [3]
If you want, I can check the current @tailwindcss/vite npm release notes or the Tailwind repo now to see whether a new version adding Vite 7 support has been published.
🌐 Web query:
vite-plugin-solid Vite 7.3.1 compatibility
💡 Result:
Short answer: Not officially—vite-plugin-solid hasn't been published with a Vite 7 peerDependency range (issues requesting Vite 7 support are open). You can force-install (e.g., --legacy-peer-deps or override peer deps) but there is no official release explicitly declaring compatibility as of Jan 18, 2026. [1][2]
Sources:
- vite-plugin-solid GitHub issues (request for Vite 7 support). [1]
- vite-plugin-solid npm / package info. [2]
Vite 7.3.1 bump blocked by incompatible plugins.
Vite 7.3.1 is a safe patch release with no breaking changes. However, @tailwindcss/vite and vite-plugin-solid do not yet have official Vite 7 support—both still declare peer dependencies for Vite 5/6 only. Using them with Vite 7.3.1 will trigger peer-dependency errors. Either downgrade Vite to 6.x or wait for these plugins to publish Vite 7 support before merging.
🤖 Prompt for AI Agents
In `@examples/solid/start-tailwind-v4/package.json` at line 25, The package.json
currently pins "vite": "^7.3.1" which is incompatible with the project's plugins
(`@tailwindcss/vite` and vite-plugin-solid) that only declare Vite 5/6 peer deps;
change the Vite dependency back to a compatible 6.x version (e.g., update the
"vite" entry to a 6.x semver like "^6.X.Y" or the previous working version) so
the peer-dependency constraints for `@tailwindcss/vite` and vite-plugin-solid are
satisfied, or alternatively hold the Vite bump until those plugins publish Vite
7 support.
There was a problem hiding this comment.
Actionable comments posted: 3
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (14)
e2e/react-router/i18n-paraglide/package.json (1)
15-24: Switch internal workspace deps toworkspace:*.Repository guidance requires
workspace:*for internal dependencies;workspace:^should be updated.♻️ Proposed fix
- "@tanstack/react-router": "workspace:^", + "@tanstack/react-router": "workspace:*", ... - "@tanstack/router-e2e-utils": "workspace:^", - "@tanstack/router-plugin": "workspace:^", + "@tanstack/router-e2e-utils": "workspace:*", + "@tanstack/router-plugin": "workspace:*",As per coding guidelines, use
workspace:*for internal dependencies.e2e/react-start/spa-mode/package.json (1)
15-23: Useworkspace:*for internal@tanstackdeps.Internal dependencies should use the workspace protocol with
*instead of^.♻️ Proposed fix
- "@tanstack/react-router": "workspace:^", - "@tanstack/react-router-devtools": "workspace:^", - "@tanstack/react-start": "workspace:^", + "@tanstack/react-router": "workspace:*", + "@tanstack/react-router-devtools": "workspace:*", + "@tanstack/react-start": "workspace:*", ... - "@tanstack/router-e2e-utils": "workspace:^", + "@tanstack/router-e2e-utils": "workspace:*",As per coding guidelines, use
workspace:*for internal dependencies.e2e/solid-start/basic-solid-query/package.json (1)
17-30: Switch internal workspace deps toworkspace:*.Internal TanStack packages should use
workspace:*to align with repo guidelines.♻️ Proposed fix
- "@tanstack/solid-router": "workspace:^", - "@tanstack/solid-router-devtools": "workspace:^", - "@tanstack/solid-router-ssr-query": "workspace:^", - "@tanstack/solid-start": "workspace:^", + "@tanstack/solid-router": "workspace:*", + "@tanstack/solid-router-devtools": "workspace:*", + "@tanstack/solid-router-ssr-query": "workspace:*", + "@tanstack/solid-start": "workspace:*", ... - "@tanstack/router-e2e-utils": "workspace:^", + "@tanstack/router-e2e-utils": "workspace:*",As per coding guidelines, use
workspace:*for internal dependencies.examples/react/with-framer-motion/package.json (1)
22-27: Upgrade@vitejs/plugin-reactto v5 or later for Vite 7 compatibility.
@vitejs/plugin-react4.3.4 does not support Vite 7. Version 5 or later is required to work with Vite 7.3.1.e2e/react-router/basic-react-query/package.json (1)
24-30: Upgrade@vitejs/plugin-reactto v5+ for Vite 7.3.1 compatibility.Vite 7.3.1 requires Node.js 20.19+ or 22.12+. More importantly,
@vitejs/plugin-reactv4.x does not officially support Vite 7 (peer dependency limited to Vite 6). Vite 7 support was added in@vitejs/plugin-reactv5+. Update@vitejs/plugin-reactfrom^4.3.4to^5.0.0or later.examples/solid/start-convex-better-auth/package.json (1)
16-18: Use workspace: for internal TanStack packages.*These appear to be workspace packages and should use the workspace protocol for consistency and local linking.
🔧 Suggested update
- "@tanstack/solid-router": "^1.151.2", - "@tanstack/solid-router-devtools": "^1.151.2", - "@tanstack/solid-start": "^1.151.2", + "@tanstack/solid-router": "workspace:*", + "@tanstack/solid-router-devtools": "workspace:*", + "@tanstack/solid-start": "workspace:*",As per coding guidelines, internal dependencies in package.json should use workspace:*.
e2e/vue-start/basic-auth/package.json (1)
19-21: Use workspace: for internal TanStack packages.*These are internal workspace packages; use the workspace protocol rather than workspace:^.
🔧 Suggested update
- "@tanstack/vue-router": "workspace:^", - "@tanstack/vue-router-devtools": "workspace:^", - "@tanstack/vue-start": "workspace:^", + "@tanstack/vue-router": "workspace:*", + "@tanstack/vue-router-devtools": "workspace:*", + "@tanstack/vue-start": "workspace:*", ... - "@tanstack/router-e2e-utils": "workspace:^", + "@tanstack/router-e2e-utils": "workspace:*",As per coding guidelines, internal dependencies in package.json should use workspace:*.
Also applies to: 30-30
e2e/react-router/basic-virtual-file-based/package.json (1)
15-18: Use workspace: for internal TanStack packages.*These are internal workspace packages and should use workspace:* rather than workspace:^.
🔧 Suggested update
- "@tanstack/react-router": "workspace:^", - "@tanstack/react-router-devtools": "workspace:^", - "@tanstack/router-plugin": "workspace:^", - "@tanstack/virtual-file-routes": "workspace:^", + "@tanstack/react-router": "workspace:*", + "@tanstack/react-router-devtools": "workspace:*", + "@tanstack/router-plugin": "workspace:*", + "@tanstack/virtual-file-routes": "workspace:*", ... - "@tanstack/router-e2e-utils": "workspace:^", + "@tanstack/router-e2e-utils": "workspace:*",As per coding guidelines, internal dependencies in package.json should use workspace:*.
Also applies to: 27-27
examples/react/start-workos/package.json (1)
17-19: Use workspace: for internal TanStack packages.*These look like internal workspace packages; use the workspace protocol instead of fixed version ranges.
🔧 Suggested update
- "@tanstack/react-router": "^1.151.2", - "@tanstack/react-router-devtools": "^1.151.2", - "@tanstack/react-start": "^1.151.2", + "@tanstack/react-router": "workspace:*", + "@tanstack/react-router-devtools": "workspace:*", + "@tanstack/react-start": "workspace:*",As per coding guidelines, internal dependencies in package.json should use workspace:*.
examples/react/start-basic-rsc/package.json (1)
13-15: Use workspace: for internal TanStack packages.*These appear to be internal workspace packages and should use workspace:*.
🔧 Suggested update
- "@tanstack/react-router": "^1.151.2", - "@tanstack/react-router-devtools": "^1.151.2", - "@tanstack/react-start": "^1.151.2", + "@tanstack/react-router": "workspace:*", + "@tanstack/react-router-devtools": "workspace:*", + "@tanstack/react-start": "workspace:*",As per coding guidelines, internal dependencies in package.json should use workspace:*.
e2e/vue-start/basic-vue-query/package.json (1)
17-20: Useworkspace:*for internal dependencies.Repo guideline requires
workspace:*for internal packages.♻️ Proposed fix
- "@tanstack/vue-router": "workspace:^", - "@tanstack/vue-router-devtools": "workspace:^", - "@tanstack/vue-router-ssr-query": "workspace:^", - "@tanstack/vue-start": "workspace:^", + "@tanstack/vue-router": "workspace:*", + "@tanstack/vue-router-devtools": "workspace:*", + "@tanstack/vue-router-ssr-query": "workspace:*", + "@tanstack/vue-start": "workspace:*", @@ - "@tanstack/router-e2e-utils": "workspace:^", + "@tanstack/router-e2e-utils": "workspace:*",Also applies to: 30-30
e2e/solid-start/serialization-adapters/package.json (1)
15-17: Useworkspace:*for internal dependencies.Repo guideline requires
workspace:*for internal packages.♻️ Proposed fix
- "@tanstack/solid-router": "workspace:^", - "@tanstack/solid-router-devtools": "workspace:^", - "@tanstack/solid-start": "workspace:^", + "@tanstack/solid-router": "workspace:*", + "@tanstack/solid-router-devtools": "workspace:*", + "@tanstack/solid-start": "workspace:*", @@ - "@tanstack/router-e2e-utils": "workspace:^", + "@tanstack/router-e2e-utils": "workspace:*",Also applies to: 25-25
e2e/vue-start/custom-basepath/package.json (1)
13-25: Useworkspace:*for internal deps.Internal packages in this file still use
workspace:^(e.g., Lines 14–16 and Line 24). The repo guideline calls forworkspace:*.♻️ Proposed change
- "@tanstack/vue-router": "workspace:^", - "@tanstack/vue-router-devtools": "workspace:^", - "@tanstack/vue-start": "workspace:^", + "@tanstack/vue-router": "workspace:*", + "@tanstack/vue-router-devtools": "workspace:*", + "@tanstack/vue-start": "workspace:*",- "@tanstack/router-e2e-utils": "workspace:^", + "@tanstack/router-e2e-utils": "workspace:*",As per coding guidelines, ...
examples/solid/search-validator-adapters/package.json (1)
14-20: Use workspace protocolworkspace:*for@tanstackinternal dependencies.The
@tanstackpackages should use the workspace protocol to ensure consistency with other parts of the monorepo. Update all@tanstackdependencies on lines 14-20 from^1.151.2toworkspace:*."@tanstack/arktype-adapter": "workspace:*", "@tanstack/solid-query": "workspace:*", "@tanstack/solid-router": "workspace:*", "@tanstack/solid-router-devtools": "workspace:*", "@tanstack/router-plugin": "workspace:*", "@tanstack/valibot-adapter": "workspace:*", "@tanstack/zod-adapter": "workspace:*",
🤖 Fix all issues with AI agents
In `@e2e/react-start/css-modules/package.json`:
- Line 46: The "vite" dependency in package.json is set to a non-existent
version "^7.3.1"; update the dependency entry for "vite" in package.json to a
valid published version (e.g., change the value to "^7.1.4") so installs won't
fail—locate the "vite" entry in the dependencies/devDependencies section and
replace "^7.3.1" with "^7.1.4" (or another valid semver) and run a fresh install
to verify.
In `@e2e/react-start/serialization-adapters/package.json`:
- Around line 20-21: The package.json currently lists "vite" and
"vite-tsconfig-paths" under dependencies; move these two entries into
devDependencies instead (remove them from the "dependencies" object and add
them, with the same version strings "^7.3.1" and "^5.1.4", to the
"devDependencies" object) so build tools are not shipped as runtime deps; update
the package.json's dependency sections accordingly.
In `@packages/router-devtools-core/package.json`:
- Around line 69-72: package.json currently lists vite 7.3.1 which requires
Node.js 20.19+ or 22.12+; update the package.json "engines" field to reflect the
minimum supported Node version (e.g., "node": ">=20.19" or a range ">=20.19 ||
>=22.12") and ensure any CI workflow files that set a Node version (look for
"node-version" or matrix entries in files under .github/workflows, or references
to setup-node in workflows) are updated to use the same minimums in their matrix
entries (replace any 18.x entries and add 20.19/22.12 as needed) so the runtime
requirement and CI matrix align with Vite 7.3.1.
♻️ Duplicate comments (10)
examples/solid/start-convex-better-auth/package.json (1)
33-33: Vite bump—same verification as earlier.What is the latest Vite version, and what are the release notes or breaking changes for Vite 7.3.1?e2e/vue-start/basic-auth/package.json (1)
24-24: Vite bump—same verification as earlier.What is the latest Vite version, and what are the release notes or breaking changes for Vite 7.3.1?e2e/react-router/basic-virtual-file-based/package.json (1)
31-31: Vite bump—same verification as earlier.What is the latest Vite version, and what are the release notes or breaking changes for Vite 7.3.1?examples/react/start-workos/package.json (1)
31-31: Vite bump—same verification as earlier.What is the latest Vite version, and what are the release notes or breaking changes for Vite 7.3.1?examples/react/start-basic-rsc/package.json (1)
27-27: Vite bump—same verification as earlier.What is the latest Vite version, and what are the release notes or breaking changes for Vite 7.3.1?e2e/react-start/server-functions-global-middleware/package.json (1)
19-19: Duplicate: Vite 7.3.1 verification.Same Vite bump as earlier—please ensure compatibility with current tooling and plugins.
e2e/react-start/custom-basepath/package.json (1)
36-36: Duplicate: Vite 7.3.1 verification.Same Vite bump as earlier—please ensure compatibility with current tooling and plugins.
e2e/solid-start/csp/package.json (1)
17-17: Duplicate: Vite 7.3.1 verification.Same Vite bump as earlier—please ensure compatibility with current tooling and plugins.
e2e/solid-router/generator-cli-only/package.json (1)
26-26: Duplicate: Vite 7.3.1 verification.Same Vite bump as earlier—please ensure compatibility with current tooling and plugins.
examples/solid/router-monorepo-simple/packages/router/package.json (1)
21-21: Duplicate: Vite 7.3.1 verification.Same Vite bump as earlier—please ensure compatibility with current tooling and plugins.
🧹 Nitpick comments (6)
e2e/vue-router/basic-scroll-restoration/package.json (1)
15-16: Useworkspace:*for internal workspace deps.These internal packages are using
workspace:^, but the guideline requiresworkspace:*to keep resolution aligned with the workspace version.♻️ Suggested update
- "@tanstack/vue-router": "workspace:^", - "@tanstack/vue-router-devtools": "workspace:^", + "@tanstack/vue-router": "workspace:*", + "@tanstack/vue-router-devtools": "workspace:*", ... - "@tanstack/router-e2e-utils": "workspace:^", + "@tanstack/router-e2e-utils": "workspace:*",As per coding guidelines, internal deps should use
workspace:*.Also applies to: 24-24
examples/react/kitchen-sink-file-based/package.json (1)
12-16: Useworkspace:*for internal TanStack deps.These are internal packages and should use the workspace protocol to avoid drift. As per coding guidelines, please switch them to
workspace:*.♻️ Suggested update
- "@tanstack/react-router": "^1.151.2", - "@tanstack/react-router-devtools": "^1.151.2", - "@tanstack/router-plugin": "^1.151.2", + "@tanstack/react-router": "workspace:*", + "@tanstack/react-router-devtools": "workspace:*", + "@tanstack/router-plugin": "workspace:*",examples/solid/basic-non-nested-devtools/package.json (1)
12-15: Useworkspace:*for internal TanStack deps.These are internal packages and should use the workspace protocol to avoid drift. As per coding guidelines, please switch them to
workspace:*.♻️ Suggested update
- "@tanstack/solid-router": "^1.151.2", - "@tanstack/solid-router-devtools": "^1.151.2", + "@tanstack/solid-router": "workspace:*", + "@tanstack/solid-router-devtools": "workspace:*",e2e/solid-router/js-only-file-based/package.json (1)
14-25: Useworkspace:*for internal TanStack deps.Workspace protocol should be
workspace:*for internal packages to avoid version skew. As per coding guidelines, please update these entries.♻️ Suggested update
- "@tanstack/solid-router": "workspace:^", - "@tanstack/solid-router-devtools": "workspace:^", + "@tanstack/solid-router": "workspace:*", + "@tanstack/solid-router-devtools": "workspace:*", @@ - "@tanstack/router-e2e-utils": "workspace:^", - "@tanstack/router-plugin": "workspace:^", + "@tanstack/router-e2e-utils": "workspace:*", + "@tanstack/router-plugin": "workspace:*",examples/solid/router-monorepo-solid-query/package.json (1)
13-18: Useworkspace:*for internal TanStack deps.These are internal packages and should use the workspace protocol to avoid drift. As per coding guidelines, please switch them to
workspace:*.♻️ Suggested update
- "@tanstack/solid-query": "^5.90.9", - "@tanstack/solid-query-devtools": "^5.90.0", - "@tanstack/solid-router": "^1.151.2", - "@tanstack/solid-router-devtools": "^1.151.2", - "@tanstack/router-plugin": "^1.151.2", + "@tanstack/solid-query": "workspace:*", + "@tanstack/solid-query-devtools": "workspace:*", + "@tanstack/solid-router": "workspace:*", + "@tanstack/solid-router-devtools": "workspace:*", + "@tanstack/router-plugin": "workspace:*",e2e/solid-router/basepath-file-based/package.json (1)
14-22: Useworkspace:*for internal TanStack deps.Workspace protocol should be
workspace:*for internal packages to avoid version skew. As per coding guidelines, please update these entries.♻️ Suggested update
- "@tanstack/solid-router": "workspace:^", - "@tanstack/solid-router-devtools": "workspace:^", - "@tanstack/router-plugin": "workspace:^", + "@tanstack/solid-router": "workspace:*", + "@tanstack/solid-router-devtools": "workspace:*", + "@tanstack/router-plugin": "workspace:*", @@ - "@tanstack/router-e2e-utils": "workspace:^", + "@tanstack/router-e2e-utils": "workspace:*",
| "srvx": "^0.10.0", | ||
| "typescript": "^5.7.2", | ||
| "vite": "^7.1.7", | ||
| "vite": "^7.3.1", |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
Vite 7.3.1 release notes breaking changes
💡 Result:
There are no breaking changes in v7.3.1 — it's a patch release. See the v7.3.1 package CHANGELOG and the Vite releases page for details. [1][2]
Sources:
- Vite CHANGELOG (v7.3.1). [1]
- Vite releases page (releases/tags). [2]
🌐 Web query:
latest Vite version 2026
💡 Result:
As of Jan 18, 2026 the latest published Vite release on npm is v7.1.4. [1]
Sources:
- npm package page for vite (shows v7.1.4, last published 4 days ago). [1]
- Vite blog announcing Vite 6 (for context on recent major). [2]
If you want to double-check locally: run npm view vite version.
Vite version mismatch: v7.3.1 does not exist. The latest Vite release as of January 2026 is v7.1.4. Change the version to "^7.1.4" or the appropriate version that exists on npm to avoid installation failures.
🤖 Prompt for AI Agents
In `@e2e/react-start/css-modules/package.json` at line 46, The "vite" dependency
in package.json is set to a non-existent version "^7.3.1"; update the dependency
entry for "vite" in package.json to a valid published version (e.g., change the
value to "^7.1.4") so installs won't fail—locate the "vite" entry in the
dependencies/devDependencies section and replace "^7.3.1" with "^7.1.4" (or
another valid semver) and run a fresh install to verify.
| "vite": "^7.3.1", | ||
| "vite-tsconfig-paths": "^5.1.4", |
There was a problem hiding this comment.
Move vite and vite-tsconfig-paths to devDependencies.
These are build tools and should be in devDependencies, not dependencies. This is inconsistent with all other e2e packages in this PR.
Suggested fix
"dependencies": {
"@tanstack/react-router": "workspace:^",
"@tanstack/react-router-devtools": "workspace:^",
"@tanstack/react-start": "workspace:^",
"react": "^19.0.0",
"react-dom": "^19.0.0",
- "vite": "^7.3.1",
- "vite-tsconfig-paths": "^5.1.4",
"zod": "^3.24.2"
},
"devDependencies": {
"@tailwindcss/vite": "^4.1.18",
"@tanstack/router-e2e-utils": "workspace:^",
"@types/node": "^22.10.2",
"@types/react": "^19.0.8",
"@types/react-dom": "^19.0.3",
"@vitejs/plugin-react": "^4.3.4",
"srvx": "^0.10.0",
"tailwindcss": "^4.1.18",
- "typescript": "^5.7.2"
+ "typescript": "^5.7.2",
+ "vite": "^7.3.1",
+ "vite-tsconfig-paths": "^5.1.4"
}📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| "vite": "^7.3.1", | |
| "vite-tsconfig-paths": "^5.1.4", | |
| "dependencies": { | |
| "@tanstack/react-router": "workspace:^", | |
| "@tanstack/react-router-devtools": "workspace:^", | |
| "@tanstack/react-start": "workspace:^", | |
| "react": "^19.0.0", | |
| "react-dom": "^19.0.0", | |
| "zod": "^3.24.2" | |
| }, | |
| "devDependencies": { | |
| "@tailwindcss/vite": "^4.1.18", | |
| "@tanstack/router-e2e-utils": "workspace:^", | |
| "@types/node": "^22.10.2", | |
| "@types/react": "^19.0.8", | |
| "@types/react-dom": "^19.0.3", | |
| "@vitejs/plugin-react": "^4.3.4", | |
| "srvx": "^0.10.0", | |
| "tailwindcss": "^4.1.18", | |
| "typescript": "^5.7.2", | |
| "vite": "^7.3.1", | |
| "vite-tsconfig-paths": "^5.1.4" | |
| } |
🤖 Prompt for AI Agents
In `@e2e/react-start/serialization-adapters/package.json` around lines 20 - 21,
The package.json currently lists "vite" and "vite-tsconfig-paths" under
dependencies; move these two entries into devDependencies instead (remove them
from the "dependencies" object and add them, with the same version strings
"^7.3.1" and "^5.1.4", to the "devDependencies" object) so build tools are not
shipped as runtime deps; update the package.json's dependency sections
accordingly.
| "devDependencies": { | ||
| "solid-js": "^1.9.10", | ||
| "vite": "^7.1.7", | ||
| "vite": "^7.3.1", | ||
| "vite-plugin-solid": "^2.11.10" |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
Vite 7.3.1 Node.js version requirement minimum
💡 Result:
Vite 7.x (including 7.3.1) requires Node.js 20.19+ (or 22.12+). [1][2]
Sources:
- Vite 7 announcement (Node.js 20.19+ or 22.12+). [1]
- Vite releases page (7.x requirements). [2]
🌐 Web query:
vite-plugin-solid 2.11.10 Vite 7 compatibility
💡 Result:
Yes — vite-plugin-solid v2.11.10 is compatible with Vite 7. The plugin added Vite 7 support in the 2.11.8 series and 2.11.10 includes fixes for Vite 7+ behavior. [1][2]
Sources:
[1] vite-plugin-solid changelog (v2.11.x).
[2] vite-plugin-solid package listing (v2.11.10).
🌐 Web query:
Vite 7 breaking changes Node.js runtime requirements
💡 Result:
Vite 7 requires Node.js 20.19+ or 22.12+ and drops Node.js 18 (EOL end of April 2025). The bump is to allow Vite to be distributed ESM‑only and rely on Node’s native require(esm) support. [1][2]
Sources:
- Vite 7 announcement (Node.js support: 20.19+, 22.12+; dropped Node 18). [1]
- Vite migration notes / docs confirming Node.js 20.19+ / 22.12+ requirement. [2]
Confirm Node.js version requirement for Vite 7.3.1.
Vite 7.3.1 requires Node.js 20.19+ or 22.12+ and drops support for Node.js 18. Verify that the engines field and CI matrix are aligned with this requirement.
(Note: vite-plugin-solid 2.11.10 is confirmed compatible with Vite 7, no concern there.)
🤖 Prompt for AI Agents
In `@packages/router-devtools-core/package.json` around lines 69 - 72,
package.json currently lists vite 7.3.1 which requires Node.js 20.19+ or 22.12+;
update the package.json "engines" field to reflect the minimum supported Node
version (e.g., "node": ">=20.19" or a range ">=20.19 || >=22.12") and ensure any
CI workflow files that set a Node version (look for "node-version" or matrix
entries in files under .github/workflows, or references to setup-node in
workflows) are updated to use the same minimums in their matrix entries (replace
any 18.x entries and add 20.19/22.12 as needed) so the runtime requirement and
CI matrix align with Vite 7.3.1.
Summary by CodeRabbit
✏️ Tip: You can customize this high-level summary in your review settings.