Group layouts not working in turbopack

[joacub]

Verify canary release

• I verified that the issue exists in the latest Next.js canary release

Provide environment information

Last canary version 13.4.10-6

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

[balazsorban44]

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! 🙏

[github-actions]

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 please add a complete reproduction label?

To be able to investigate, we need access to a reproduction to identify what triggered the issue. We prefer a link to a public GitHub repository (template for pages, template for App Router), but you can also use these templates: CodeSandbox: pages or CodeSandbox: App Router.

To make sure the issue is resolved as quickly as possible, please make sure that the reproduction is as minimal as possible. This means that you should remove unnecessary code, files, and dependencies that do not contribute to the issue.

Please test your reproduction against the latest version of Next.js (next@canary) to make sure your issue has not already been fixed.

I added a link, why was it still marked?

Ensure the link is pointing to a codebase that is accessible (e.g. not a private repository). "example.com", "n/a", "will add later", etc. are not acceptable links -- we need to see a public codebase. See the above section for accepted links.

What happens if I don't provide a sufficient minimal reproduction?

Issues with the please add a complete reproduction label that receives no meaningful activity (e.g. new comments with a reproduction link) are automatically closed and locked after 30 days.

If your issue has not been resolved in that time and it has been closed/locked, please open a new issue with the required reproduction.

I did not open this issue, but it is relevant to me, what can I do to help?

Anyone experiencing the same issue is welcome to provide a minimal reproduction following the above steps. Furthermore, you can upvote the issue using the 👍 reaction on the topmost comment (please do not comment "I have the same issue" without reproduction steps). Then, we can sort issues by votes to prioritize.

I think my reproduction is good enough, why aren't you looking into it quicker?

We look into every Next.js issue and constantly monitor open issues for new comments.

However, sometimes we might miss one or two due to the popularity/high traffic of the repository. We apologize, and kindly ask you to refrain from tagging core maintainers, as that will usually not result in increased priority.

Upvoting issues to show your interest will help us prioritize and address them as quickly as possible. That said, every issue is important to us, and if an issue gets closed by accident, we encourage you to open a new one linking to the old issue and we will look into it.

Useful Resources

• How to Contribute to Open Source (Next.js)
• How to create a Minimal, Complete, and Verifiable example
• Reporting a Next.js bug
• Next.js Triaging issues

[joacub]

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! 🙏

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.
😃
any ways thanks for the response and have a good day.

[joacub]

#52650

[balazsorban44]

is the explanation of the issue not enough to understand the issue and check

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.

[joacub]

is the explanation of the issue not enough to understand the issue and check

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]

this may help:

Non matching path (es) provided for /[lang]/(main)

Debug info:
- Execution of get_from_source failed
- Execution of resolve_source_request failed
- Execution of NodeRenderContentSource::get failed
- Non matching path (es) provided for /[lang]/(main)

[axelvaindal]

@joacub @balazsorban44
Here is a reproduction you can clone, this bug is kinda easy to reproduce and we encountered it as well by trying out turbopack in our existing project with a route group.

Repro steps:

1. Clone this repository:
   https://github.com/axelvaindal/52621-turbopack-group-route

2. npm run dev

3. Open project in browser and shows the error in the screen