Conversation
## Current Behavior Creating a custom React workspace with React Router for server rendering fails due to peer dependency conflicts between Vite 8 and React Router. ## Expected Behavior The React application generator uses Vite 7 when React Router is selected, avoiding the peer dependency conflict until React Router adds Vite 8 support. ## Related Issue(s) Fixes NXC-4176
✅ Deploy Preview for nx-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for nx-dev ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Contributor
|
View your CI Pipeline Execution ↗ for commit 09e6646
☁️ Nx Cloud last updated this comment at |
FrozenPandaz
approved these changes
Mar 31, 2026
vsavkin
pushed a commit
that referenced
this pull request
Mar 31, 2026
…35101) ## Current Behavior Creating a custom React workspace with React Router for server rendering (framework mode) fails due to a peer dependency conflict between Vite 8 and React Router. Vite 8 is the current default for new workspaces, but `@react-router/dev` does not yet support it. ## Expected Behavior The React application generator uses Vite 7 when React Router is selected, avoiding the peer dependency conflict until React Router adds Vite 8 support. <img width="1270" height="1204" alt="image" src="https://github.com/user-attachments/assets/87495e85-20df-4086-a1f0-eb3380a78771" /> ## Related Issue(s) Fixes NXC-4176
FrozenPandaz
pushed a commit
that referenced
this pull request
Mar 31, 2026
…35101) ## Current Behavior Creating a custom React workspace with React Router for server rendering (framework mode) fails due to a peer dependency conflict between Vite 8 and React Router. Vite 8 is the current default for new workspaces, but `@react-router/dev` does not yet support it. ## Expected Behavior The React application generator uses Vite 7 when React Router is selected, avoiding the peer dependency conflict until React Router adds Vite 8 support. <img width="1270" height="1204" alt="image" src="https://github.com/user-attachments/assets/87495e85-20df-4086-a1f0-eb3380a78771" /> ## Related Issue(s) Fixes NXC-4176 (cherry picked from commit 2cfc289)
FrozenPandaz
added a commit
that referenced
this pull request
Apr 1, 2026
… conflict (#35110) ## Current Behavior The react-router typecheck e2e test fails in CI because pnpm resolves both vite 7 and vite 8 in the generated project. `@react-router/dev` picks up vite 8 plugin types while `defineConfig` uses vite 7 types, causing a TypeScript incompatibility. ## Expected Behavior The test is skipped until `@react-router/dev` adds Vite 8 support, at which point the `useViteV7` workaround and this skip can both be removed. ## Related Issue(s) Follow-up to #35101
vsavkin
pushed a commit
that referenced
this pull request
Apr 1, 2026
… conflict (#35110) ## Current Behavior The react-router typecheck e2e test fails in CI because pnpm resolves both vite 7 and vite 8 in the generated project. `@react-router/dev` picks up vite 8 plugin types while `defineConfig` uses vite 7 types, causing a TypeScript incompatibility. ## Expected Behavior The test is skipped until `@react-router/dev` adds Vite 8 support, at which point the `useViteV7` workaround and this skip can both be removed. ## Related Issue(s) Follow-up to #35101
FrozenPandaz
added a commit
that referenced
this pull request
Apr 1, 2026
… conflict (#35110) ## Current Behavior The react-router typecheck e2e test fails in CI because pnpm resolves both vite 7 and vite 8 in the generated project. `@react-router/dev` picks up vite 8 plugin types while `defineConfig` uses vite 7 types, causing a TypeScript incompatibility. ## Expected Behavior The test is skipped until `@react-router/dev` adds Vite 8 support, at which point the `useViteV7` workaround and this skip can both be removed. ## Related Issue(s) Follow-up to #35101 (cherry picked from commit 6962a3d)
Contributor
|
This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Current Behavior
Creating a custom React workspace with React Router for server rendering (framework mode) fails due to a peer dependency conflict between Vite 8 and React Router. Vite 8 is the current default for new workspaces, but
@react-router/devdoes not yet support it.Expected Behavior
The React application generator uses Vite 7 when React Router is selected, avoiding the peer dependency conflict until React Router adds Vite 8 support.
Related Issue(s)
Fixes NXC-4176