Repository navigation
Tanstack Router doesn't work with Parcel anymore #6184
Description
Which project does this relate to?
Router
Describe the bug
It is impossible to start the application (in dev mode), you get the following error:
`@parcel/core: Failed to resolve 'seroval-plugins/web' from './node_modules/@tanstack/react-router/node_modules/@tanstack/router-core/dist/esm/ssr/serializer/seroval-plugins.js'
`
Your Example Website or App
https://stackblitz.com/edit/vitejs-vite-c28vux18?file=package.json
Steps to Reproduce the Bug or Issue
The URL above doesn't really work because apparently Stackblitz cannot run Parcel projects but you can see my files there. In any case, it is easy to reproduce this bug:
- Create a React project with the files described in the "Manual Setup" section of the Tanstack Router documentation
- Add Router CLI and Parcel
- Try to run this project
Expected behavior
I expected the application to start but it did not.
Screenshots or Videos
No response
Platform
- Router / Start Version: 1.142.8
- OS: Windows 11
- Browser: Doesn't matter, the app fails before it gets to the browser
- Bundler: Parcel
- Bundler Version: 2.16.3
Additional context
I am using the latest versions for all libraries.
Activity
coderabbitai commentedon Dec 22, 2025
📝 CodeRabbit Plan Mode
Generate an implementation plan and prompts that you can use with your favorite coding agent.
Examples
🔗 Similar Issues
Related Issues
🔗 Related PRs
#5422 - fix(router-devtools-core): actually bundle solid [merged]
#5650 - fix: fix static server functions [merged]
#5847 - docs(solid-start): start-large example [merged]
#6026 - fix(router-devtools): move vite to devDependencies [merged]
👤 Suggested Assignees
🧪 Issue enrichment is currently in open beta.
You can configure auto-planning by selecting labels in the issue_enrichment configuration.
To disable automatic issue enrichment, add the following to your
.coderabbit.yaml:💬 Have feedback or questions? Drop into our discord or schedule a call!
schiller-manuel commentedon Dec 22, 2025
this is caused by parcel not having package exports enabled by default, see https://parceljs.org/features/dependency-resolution/#enabling-package-exports
adding this to the package.json fixes this