Next.js developers face errors with parallel routing
10 posts since Jan 2024, all from GitHub.
“Link to the code that reproduces this issue https://github.com/juliusmarminge/next intercepting routes To Reproduce 1. Start the dev server 2. Navigate to the parallel segment (e.g http://localhost:3000/dashboard/1/1) 3. Click on a card, it opens in a modal 4. Now suppose we…”
“Link to the code that reproduces this issue https://codesandbox.io/p/devbox/gallant kalam 2xqmnr?workspaceId=08193210 3c43 4dee 852a 15fcfd6a6e98 To Reproduce Fork the sandbox to see error in terminal. If you have parallel routes defined somewhere in the project and put it…”
“Verify canary release [X] I verified that the issue exists in the latest Next.js canary release Provide environment information Which example does this report relate to? https://github.com/rexfordessilfie/next tabs What browser are you using? (if relevant) No response How are…”
Developers are encountering issues when navigating away from 'Not Found' pages and experiencing unexpected remounting of memoed components, particularly within projects utilizing parallel routes.
SOURCES (10)
“Link to the code that reproduces this issue https://github.com/juliusmarminge/next intercepting routes To Reproduce 1. Start the dev server 2. Navigate to the parallel segment (e.g http://localhost:3000/dashboard/1/1) 3. Click on a card, it opens in a modal 4. Now suppose we change the URL structure, so…”
“Link to the code that reproduces this issue https://codesandbox.io/p/devbox/gallant kalam 2xqmnr?workspaceId=08193210 3c43 4dee 852a 15fcfd6a6e98 To Reproduce Fork the sandbox to see error in terminal. If you have parallel routes defined somewhere in the project and put it inside layout, eventhough it successfully redirects, nextjs throws error when inside notfound page with a link. I have tried my best to log what's undefined at 0 index, NextJS gives this : { children: [ '/ not found', { childr”
“Verify canary release [X] I verified that the issue exists in the latest Next.js canary release Provide environment information Which example does this report relate to? https://github.com/rexfordessilfie/next tabs What browser are you using? (if relevant) No response How are you deploying your application? (if relevant) No response Describe the Bug When navigating through the application, the following sequence of actions leads to the sub a route being mounted: 1. Starting from the root, naviga”
“Link to the code that reproduces this issue https://github.com/vaneenige/next app router singleton To Reproduce 1. Set a new key in the global object 2. Try to get this key from the global object inside generateStaticParams Current vs. Expected behavior I expected the global object to be the same in this environment Provide environment information Which area(s) are affected? (Select all that apply) Performance, Runtime Which stage(s) are affected? (Select all that apply) next dev (local), next b”
“Link to the code that reproduces this issue https://github.com/dalkommatt/redirect parallel route infinite reload To Reproduce 1. pnpm dlx create next app@rc 2. Create @modal parallel route with (.)login, catchAll and default image 3. Create a /login route image 4. redirect('/login') from '/' Current vs. Expected behavior Current: Infinitely reloads /login Expected: Opens model route Provide environment information Which area(s) are affected? (Select all that apply) create next app, Navigation,”
“Link to the code that reproduces this issue https://github.com/marmalade labs/parallel route rerender To Reproduce 1. Create production build of the application ( bun run build && bun start ) or navigate to https://parallel route rerender.vercel.app/a 2. Click on one of the cards in the bottom half of the page Current vs. Expected behavior Current Behavior If you open the Network tab in DevTools, when you click a card you will see 21 fetches for the current route (with different ? rsc= params),”
“Link to the code that reproduces this issue https://github.com/DominikMeca/nextjs intercept reproduction To Reproduce 1. Start the application in dev ( npm run dev ) 2. Manually navigate to /working/id 3. Click on Client Side navigation to Target 4. Observe it working 5. Manually navigate to /notworking/id (or any other id/slug/...) 3. Click on Client Side navigation to Target 4. Observe being fully navigated to the target page Current vs. Expected behavior I expect the modal text to show up on”
“Link to the code that reproduces this issue https://github.com/spencerwilson/nextjs maxDuration repro To Reproduce 1. Run npm run build on https://github.com/spencerwilson/nextjs maxDuration repro/commit/c6a491b4e71bec9b98b22184e970526cab640adb and observe: 2. Run npm run build on https://github.com/spencerwilson/nextjs maxDuration repro/commit/1b5f8ee4fded20e0abac6afcf1d3c58d2e249760 and observe: The difference between those two revisions diff is that the index page's maxDuration stops being re”
“Link to the code that reproduces this issue https://github.com/MistaPidaus/nextjs routing issue To Reproduce 1. Build the app locally and run production locally 2. Open the Chrome Dev tool and set the network profile to "Slowest 3G" with 250kb for both download & upload value and 5000 for latency value 3. On the performance tab, set the CPU performance to 6x slowdown and make sure the network is the new profile with above setting. 4. Open http://localhost:3000 5. Once you see the header section”
“Link to the code that reproduces this issue https://github.com/hipstersmoothie/hipstersmoothie.com 2 To Reproduce 1. turn ppr on 2. deploy 3. cmd+k (or hit button in header) Current vs. Expected behavior Current: I think it render the non intercepted version (which in this case just redirects) Expected: The command palette appears Provide environment information Which area(s) are affected? (Select all that apply) App Router Which stage(s) are affected? (Select all that apply) Vercel (Deployed) A”