-
Notifications
You must be signed in to change notification settings - Fork 26.9k
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
Group layouts not working in turbopack #52621
Comments
Hi @joacub, I've gone through your previously reported issues, and almost all lacked a reproduction. Please note that the Next.js issue tracker is for reporting reproducible issues, and thus they need to follow the issue template. Not providing a proper reproduction makes it hard/impossible to investigate. I kindly ask you to not open more issues without following the required steps, as described in the issue template. Not following the template can result in issues being converted to discussions. If you are not certain if something is a Next.js bug, you can use Discussions, or our Discord server where community members might be able to help with debugging your project further. Thanks for understanding! 🙏 |
We cannot recreate the issue with the provided information. Please add a reproduction in order for us to be able to investigate. Why was this issue marked with the
|
Hi how are you, is the explanation of the issue not enough to understand the issue and check it, is a very simple problem group routers does not work in turbopack what a reproduction do you need. I already kindly report this to here so you guys can check and take the necessary actions if you want, this issues does not need a reproduction is very simple and straightforward. But yeah I will take your advice and do not open any new issue, I really don’t have the time to do that, I was doing trying to help but have no time to make for a simple thing a complete reproduction every single time that nextjs has bugs like this which is very often. |
There is a high volume of issues coming in, the ones that come with a reproduction help us help you the fastest. Please read #52621 (comment) for a full explanation. We absolutely don't want to discourage you from reporting valid bugs, but we rely on you and the rest of our community to cooperate for fast resolutions for everyone's success, that's why we've put effort into creating the issue template, which we expect everyone to respect and fill out accordingly. |
I completely understand your perspective and your request. Please don't misunderstand me, but I regret to inform you that I am unable to fulfill it. Due to time constraints, I am unable to engage in reproductions. Additionally, I believe that reproductions are often unnecessary as they tend to be simple in nature and can be easily resolved without the need for reproduction. But yeah i totally understand have a good one |
@joacub @balazsorban44 Repro steps:
|
Same issue. Watching. |
This comment has been minimized.
This comment has been minimized.
I'm having the same issue |
This appears to be fixed with v13.5+ |
This closed issue has been automatically locked because it had no new activity for 2 weeks. 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
Which area(s) of Next.js are affected? (leave empty if unsure)
App Router, Turbopack (--turbo)
Link to the code that reproduces this issue or a replay of the bug
No response
To Reproduce
Having this route segments will break in the home route and all routes inside group main
[lang]/(main)/page.tsx
layout.tsx
when accesing routes in main group all routes fails as there is no matching routes
In webpack works fine.
Describe the Bug
No response
Expected Behavior
No response
Which browser are you using? (if relevant)
No response
How are you deploying your application? (if relevant)
No response
WEB-1298
The text was updated successfully, but these errors were encountered: