Next.js in development mode throws a client-side exception on Safari 16.3 in version 14.2.11

[sadkebab]

Link to the code that reproduces this issue

https://github.com/sadkebab/nextjs-safari-bug

To Reproduce

1. pnpm dev
2. Open localhost:3000 on safari 16.3, it will always show a black screen with the "Application error: a client-side exception has occurred (see the browser console for more information)." message if you are using the App Router or a blank white screen if you are using the Pages Directory
3. Change version of next to 14.2.10 in package.json
4. pnpm i
5. pnpm dev
6. Open localhost:3000 on safari 16.3, it will show the default home page for a new next.js project

Current vs. Expected behavior

I should be able to run my Next application on Safari 16 while developing.

Homepage (App Router) for version 14.2.11

Homepage (Pages Directory) for version 14.2.11

Expected homepage as it was until version 14.2.10

Provide environment information

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 22.3.0: Mon Jan 30 20:39:46 PST 2023; root:xnu-8792.81.3~2/RELEASE_ARM64_T6020
  Available memory (MB): 16384
  Available CPU cores: 10
Binaries:
  Node: 22.4.0
  npm: 10.8.1
  Yarn: N/A
  pnpm: 9.9.0
Relevant Packages:
  next: 14.2.11 // Latest available version is detected (14.2.11).
  eslint-config-next: 14.2.11
  react: 18.3.1
  react-dom: 18.3.1
  typescript: 5.6.2
Next.js Config:
  output: N/A

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

Developer Experience, Testing

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

next dev (local)

Additional context

The bug seems to affect only version 14.2.11 both for App Router and Pages Directory, canary is not affected. The problem does not occur outside of next dev, meaning that if I do next build && next start the result is the expected one both as a static output and as a dynamic page generation.

[samcx]

@sadkebab Unfortunately, I am not on Safari 16.3 to test this. Working fine on Safari 18.

Is there any error in your console? It may be create-next-app related.