experimental.typedRoutes throws TS error for group routes inside dynamic routes

[AhmedBaset]

Link to the code that reproduces this issue

Code Sand Box

To Reproduce

1. see the code in app/page.tsx
2. run next build
3. the build process will not succeed.

Current vs. Expected behavior

It's supposed to catch /[locale]/(main)/page.tsx correctly as /${string}/.

Current: throws TS error.

path	href	status
(group)/page.tsx	/	✅
[dynamic]/about/(group)/page.tsx	/en/about	✅
[dynamic]/(group)/page.tsx	/en/	❌

Verify canary release

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

Provide environment information

Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 10 Home Single Language
Binaries:
  Node: 20.0.0
  npm: N/A
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: canary
  eslint-config-next: canary
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.2.2
Next.js Config:
  output: N/A

Which area(s) are affected? (Select all that apply)

TypeScript (plugin, built-in types)

Additional context

No response

[controversial]

The codesandbox reproduction you left is broken for me, however I’m running into the same bug

Running next dev creates a link.d.ts containing all my routes, however when i run next build it’s replaced by a link.d.ts containing fewer routes (excluding those that are a part of route groups)

[controversial]

I looked into the next-types-plugin source, and I found that

I found that in my case, some modules (as returned by compilation.chunkGraph.getChunkModulesIterable(chunk)) were given an empty string (or undefined) for module.resource by Webpack, instead of the actual path to the resource.

I wasn’t able to track down the cause of this bug, but I patched next-types-plugin/index.js as follows, and that seems to work for now

[controversial]

I don’t think this reproduces for me anymore; I was able to remove my patch from next-types-plugin.

[huozhi]

Close per #58226 (comment)
As the orginal codesandbox repro is not valid anymore

[github-actions]

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.