Test again..

[samcx]

Link to the code that reproduces this issue

https://github.com/samcx/samcx

To Reproduce

Test again..

Current vs. Expected behavior

Test again..

Provide environment information

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.5.0: Wed May  1 20:17:33 PDT 2024; root:xnu-10063.121.3~5/RELEASE_ARM64_T6031
  Available memory (MB): 49152
  Available CPU cores: 16
Binaries:
  Node: 18.19.1
  npm: 10.2.4
  Yarn: 1.22.21
  pnpm: 9.1.4
Relevant Packages:
  next: 15.0.0-canary.6 // There is a newer canary version (15.0.0-canary.12) available, please upgrade!
  eslint-config-next: 15.0.0-canary.6
  react: 19.0.0-rc-935180c7e0-20240524
  react-dom: 19.0.0-rc-935180c7e0-20240524
  typescript: 5.4.5
Next.js Config:
  output: N/A
 ⚠ There is a newer canary version (15.0.0-canary.12) available, please upgrade!
   Please try the latest canary version (`npm install next@canary`) to confirm the issue still exists before creating a new issue.
   Read more - https://nextjs.org/docs/messages/opening-an-issue

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

Not sure

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

next dev (local), next build (local), next start (local), Vercel (Deployed)

Additional context

No response

[github-actions]

Hello world!

[github-actions]

Hello everyone,

Here is the [bug report](https://github.com/vercel/next.js/issues/new?assignees=&labels=bug&projects=&template=1.bug_report.yml).

Thank you for your understanding and contributions!

Best regards,
The Next.js Team, @samcx

[github-actions]

Hello everyone,

Here is the bug report.

Thank you for your understanding and contributions!

Best regards,
The Next.js Team, @samcx

[github-actions]

Hi everyone!

We are currently in the process of closing older issues to keep our repository clean and focused. If you believe your issue is still relevant, we encourage you to reopen the same issue using the bug report template. If there is context in the original issue, please include it in your new issue.

Thank you for your understanding and contributions!

Best regards,
The Next.js Team

[github-actions]

Hi everyone!

We are currently in the process of closing older issues.

Why?

• Stale issues are not being actively looked at, and likely do not have a recent, minimal reproduction.
• We’re trying to prioritize our highest upvoted issues that are immediately actionable with a recent minimal reproduction—otherwise we spend lots of time trying to create reproductions when we could be addressing other bugs.

If you believe your issue is still relevant, we encourage you to reopen the same issue using the bug report template. If there is context in the original issue, please include it in your new issue.

Thank you for your understanding and contributions!

Best regards,
The Next.js Team

[github-actions]

We are in the process of closing issues dating back to 2020 to improve our focus on the most relevant and actionable problems.

Why are we doing this?

Stale issues often lack recent updates and clear reproductions, making them difficult to address effectively. Our objective is to prioritize the most upvoted and actionable issues that have up-to-date reproductions, enabling us to resolve bugs more efficiently.

Why 2020 issues?

Issues from 2020 are likely to be outdated and less relevant to the current state of the codebase. By closing these older stale issues, we can better focus our efforts on more recent and relevant problems, ensuring a more effective and streamlined workflow.

If your issue is still relevant, please reopen it using our bug report template. Be sure to include any important context from the original issue in your new report.

Thank you for your understanding and contributions.

Best regards,
The Next.js Team