You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Check the next-router-state-tree on list of headers
Current vs. Expected behavior
Current, for each parallel route we append the url and search parameters multiple times, which make it very very large request payload when there are many search parameters present e.g selecting multiple filters, this large payload is out of bounds for some servers
Expected, when not using parallel routes, it's only repeated once per page and request payload is much smaller
Link to the code that reproduces this issue
https://codesandbox.io/p/devbox/ancient-tree-q99l5x
To Reproduce
next-router-state-tree
on list of headersCurrent vs. Expected behavior
Current, for each parallel route we append the url and search parameters multiple times, which make it very very large request payload when there are many search parameters present e.g selecting multiple filters, this large payload is out of bounds for some servers
Expected, when not using parallel routes, it's only repeated once per page and request payload is much smaller
I attached an example json of the
next-router-state-tree
parallel-routes.json
Provide environment information
Node.js v22.13.1 Operating System: Platform: darwin Arch: arm64 Version: Darwin Kernel Version 24.3.0: Thu Jan 2 20:24:22 PST 2025; root:xnu-11215.81.4~3/RELEASE_ARM64_T6041 Available memory (MB): 49152 Available CPU cores: 14 Binaries: Node: 22.13.1 npm: 10.9.2 Yarn: 4.8.1 pnpm: N/A Relevant Packages: next: 15.2.3 eslint-config-next: N/A react: 19.0.0 react-dom: 19.0.0 typescript: 5.3.3 Next.js Config: output: N/A
Which area(s) are affected? (Select all that apply)
Route Groups
Which stage(s) are affected? (Select all that apply)
Other (Deployed)
Additional context
No response
The text was updated successfully, but these errors were encountered: