Incorrect routing when using generateStaticParams in standalone mode

[leanderiversen]

Link to the code that reproduces this issue

https://github.com/leanderiversen/open-next-331/

To Reproduce

1. Run next build
2. Run node .next/standalone/server.js
3. Open http://localhost:3000/en-gb/first/second/

Current vs. Expected behavior

I would expect the static route to render, as this is what happens when running next dev. In reality, the dynamic route renders.

Verify canary release

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

Provide environment information

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.3.0: Wed Dec 20 21:30:44 PST 2023; root:xnu-10002.81.5~7/RELEASE_ARM64_T6000
Binaries:
  Node: 18.19.0
  npm: 10.2.3
  Yarn: 1.22.19
  pnpm: 8.15.1
Relevant Packages:
  next: 14.1.1-canary.43 // Latest available version is detected (14.1.1-canary.43).
  eslint-config-next: 14.1.1-canary.43
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.3.3
Next.js Config:
  output: standalone

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

App Router, Standalone mode (output: "standalone")

Additional context

I did initially think that this was an OpenNext issue, but have been provided more details confirming that this is an issue with Next.

[leanderiversen]

The issue was fixed before in a canary prior to next@14.0.5-canary.39, but seems to have reappeared in a canary between 39 and 57.

[leanderiversen]

This looks to be resolved in 14.1.1-canary.15 by #61115.

[leanderiversen]

This has now been broken since 14.1.1-canary.16, caused by #61241.

[leanderiversen]

The issue has been resolved in one of the latest versions.

[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.