New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
12.1.3-canary.0 breaks catch-all dynamic routes with Edge runtime #35686
Comments
The error only seems to be happening if this is set within the page:
|
Updated my example above, does not reproduce still. Could you distill the problem into a repository and link to it so we can investigate further? 🙏 |
Here you go: next-dynamic-routes-bug. |
Thanks! I could confirm a bug, but it is not related to experimental features. I created a more minimal reproduction myself here, using React 17 and no experimental features. The only requirement for the bug to appear is The PR #32601 indeed seems to be the problem. When building the route nodes, |
Ah, interesting! Should the Removed my own repo, btw, now that you've created one too. |
Seems like the bug might've been reverted here (will test with the next stable): 9805399 |
Indeed, closing it. |
This closed issue has been automatically locked because it had no new activity for a month. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you. |
Verify canary release
Provide environment information
What browser are you using? (if relevant)
Chrome 99.0.4844.84
How are you deploying your application? (if relevant)
Vercel
Describe the Bug
Upgrading from
12.1.2-canary.1
to12.1.3-canary.0
preventsnext dev
from working:The error isn't being very clear, but I'm assuming it's complaining about one of the dynamic routes I've configured. I have to guess which one it is, since the error doesn't say that, but perhaps this one:
After removing it,
next dev
works just fine. It also worked just fine with12.1.2-canary.1
, so this seems like a bug.My guess is that it was caused by #32601 (I verified that #35451 is fixed, though, which I've reported a couple days ago).
Expected Behavior
I'd expect the behavior for the dynamic route mentioned above to be what it was with version
12.1.2-canary.1
and therefore not break when runningnext dev
.To Reproduce
/pages/[capture-a]/something/[capture-b]/[...capture-c].server.tsx
next dev
The text was updated successfully, but these errors were encountered: