Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

dynamic nested route matches where it should 404

See original GitHub issue

Bug report

Describe the bug

Give the pages structure

/pages
  /[post]
    /[comment].js
  /user
    /home.js

When you visit the url /user/non-existing it will render /[post]/[comment].js instead of 404. It’s clear that the developer intends for the /user prefix to be its own subsection, so when visiting routes in that subsection it is unexpected to match anything form the /[post] folder.

To Reproduce

Steps to reproduce the behavior, please provide code snippets or a repository:

Example at https://codesandbox.io/s/goofy-moore-mmi49
Go to /user/non-existing
Observe

Expected behavior

It should 404

Issue Analytics

State:
Created 4 years ago
Comments:5 (5 by maintainers)

Top GitHub Comments

1reaction

timneutkenscommented, Feb 16, 2020

This is expected behavior imo. You have a dynamic top level route and it matches that.

Eg if the behavior you described would be implemented zeit.co would break on user account routes / dashboard routes

0reactions

balazsorban44commented, Jan 29, 2022

This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.