generateStaticParams() not detected when using parallel routes / dynamic routes using output: export

[KoenLemmen]

generateStaticParams() not detected when using parallel routes / dynamic routes using output: export

[Syhans]

Can confirm, I have the same issue for basically the same use case. For what it's worth:

• I checked several Next 14 releases (14.1.4 (current latest), 14.0.0, 14.0.1, 14.0.3 and 14.1.1, as well as the current canary 14.2.0-canary.61) and get this behaviour with all of them.
• The app behaves as expected when not using output: "export". Which, granted, is not very helpful when the goal is to create a static site.

[NeoPrint3D]

Any Progress or updates? This issue is super dumb especially if vercel wants to ease people into using nextjs from an old codebase or vite.

[KoenLemmen]

Not that I know of. Still broken in 14.2.1-canary.6

[dylan-sharp]

I am experiencing this issue as well and I am using app router

[PArns]

My page heavily uses parallel routing, which ultimately ends in just having dynamic rendering and no SSR at all.

So adding this feature would be really beneficial -> https://patrick-arns.de

[KoenLemmen]

Looks like this issue is wrongfully tagged as pages router. I did say in the post its an app router bug.

[elmarsto]

this should be a hi-pri fix, it makes parallel routes useless for a number of important use cases, e.g. an edit modal that takes an id in the path

[KoenLemmen]

I agree. Modals in general don't work due to this, the minimal I attached is their own example.

[BuzzardM]

Upon having the same issue I stumbled on this issue. Is there a workaround (or even a fix) available for this?

Edit by maintainer bot: Comment was automatically minimized because it was considered unhelpful. (If you think this was by mistake, let us know). Please only comment if it adds context to the issue. If you want to express that you have the same problem, use the upvote 👍 on the issue description or subscribe to the issue for updates. Thanks!

[KoenLemmen]

Not yet but I'm hoping #65348 might also fix this.

Edit: checked canary up to [v14.3.0-canary.67]. Bug still present.