next.js: Regression of tippy.js between 13.4.10-canary.0 and 13.4.10-canary.1

Verify canary release

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

Provide environment information

Operating System:
  Platform: darwin
  Arch: x64
  Version: Darwin Kernel Version 22.5.0: Thu Jun  8 22:22:22 PDT 2023; root:xnu-8796.121.3~7/RELEASE_X86_64
Binaries:
  Node: 18.15.0
  npm: 9.6.6
  Yarn: 1.22.19
  pnpm: N/A
Relevant Packages:
  next: 13.4.12
  eslint-config-next: N/A
  react: 18.2.0
  react-dom: 18.2.0
  typescript: N/A
Next.js Config:
  output: N/A

Which area(s) of Next.js are affected? (leave empty if unsure)

No response

Link to the code that reproduces this issue or a replay of the bug

https://github.com/damianfrizzi/nextjs-tippy-regression

To Reproduce

• Clone the minimal repro
• Run yarn dev -> everything works fine
• Run yarn build and yarn start -> app crashes with Application error: a client-side exception has occurred (see the browser console for more information).

Describe the Bug

We tried to upgrade to the latest Next.js and it broke pages that where using @tippyjs/react. This only happens in production. Everything works correctly in development.

Git bisect shows me that the regression was introduced between 13.4.10-canary.0 (good) and 13.4.10-canary.1 (bad).

Expected Behavior

• The behaviour between development and production should be the same
• The app shouldn’t crash in production