During local development next dev, a nested page inside of a parallel route without a corresponding matched route inside another parallel route causes an infinite reload, despite the required default file meant to render as a fallback.
- install packages -
pnpm install - run next dev -
pnpm dev - navigate to
http://localhost:3000/home/nesteddirectly to experience the infinite refresh right away.- Timestamp will update on each render.
- Server logs from the middleware will populate on each reload
- alternatively, navigate to
http://localhost:3000/home/and then click on the hard navigation and/or the next link forhttp://localhost:3000/home/nested- hard navigation link refreshes infinitely
- next link behaves as expected and does not refresh infinitely
Reproduced with [email protected]
Operating System:
Platform: darwin
Arch: arm64
Version: Darwin Kernel Version 22.5.0: Thu Jun 8 22:22:23 PDT 2023; root:xnu-8796.121.3~7/RELEASE_ARM64_T6020
Binaries:
Node: 18.16.0
npm: 9.5.1
Yarn: N/A
pnpm: 8.6.5
Relevant Packages:
next: 13.4.9-canary.2
eslint-config-next: 13.4.8
react: 18.2.0
react-dom: 18.2.0
typescript: 5.1.6
Next.js Config:
output: N/A
This is a Next.js template to use when reporting a bug in the Next.js repository.
These are the steps you should follow when creating a bug report:
- Bug reports must be verified against the
next@canaryrelease. The canary version of Next.js ships daily and includes all features and fixes that have not been released to the stable version yet. Think of canary as a public beta. Some issues may already be fixed in the canary version, so please verify that your issue reproduces before opening a new issue. Issues not verified againstnext@canarywill be closed after 30 days. - Make sure your issue is not a duplicate. Use the GitHub issue search to see if there is already an open issue that matches yours. If that is the case, upvoting the other issue's first comment is desireable as we often prioritize issues based on the number of votes they receive. Note: Adding a "+1" or "same issue" comment without adding more context about the issue should be avoided. If you only find closed related issues, you can link to them using the issue number and
#, eg.:I found this related issue: #3000. - If you think the issue is not in Next.js, the best place to ask for help is our Discord community or GitHub discussions. Our community is welcoming and can often answer a project-related question faster than the Next.js core team.
- Make the reproduction as minimal as possible. Try to exclude any code that does not help reproducing the issue. E.g. if you experience problems with Routing, including ESLint configurations or API routes aren't necessary. The less lines of code is to read through, the easier it is for the Next.js team to investigate. It may also help catching bugs in your codebase before publishing an issue.
Execute create-next-app with npm, Yarn, or pnpm to bootstrap the example:
npx create-next-app --example reproduction-template reproduction-appyarn create next-app --example reproduction-template reproduction-apppnpm create next-app --example reproduction-template reproduction-appTo learn more about Next.js, take a look at the following resources:
- Next.js Documentation - learn about Next.js features and API.
- Learn Next.js - an interactive Next.js tutorial.
- How to Contribute to Open Source (Next.js) - a video tutorial by Lee Robinson
- Triaging in the Next.js repository - how we work on issues
- CodeSandbox - Edit this repository on CodeSandbox
You can check out the Next.js GitHub repository - your feedback and contributions are welcome!
If your reproduction needs to be deployed, the easiest way is to use the Vercel Platform from the creators of Next.js.
Check out our Next.js deployment documentation for more details.