Error: Should have a queue. This is likely a bug in React. Please file an issue.

[ony3000]

Verify canary release

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

Provide environment information

Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 10 Home
Binaries:
  Node: 16.13.2
  npm: N/A
  Yarn: N/A
  pnpm: N/A
Relevant packages:
  next: 13.4.2-canary.0
  eslint-config-next: 13.2.3
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 4.9.5

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

No response

Link to the code that reproduces this issue

https://github.com/ony3000/1to30/tree/error-reporting

To Reproduce

1. Start the development server for the repository link entered above and connect to http://localhost:17030/
2. Click button.
3. Open src/hooks/useGameContent.ts in the code editor, uncomment line 17 and save.

Describe the Bug

Expected Behavior

Hot module replacement without errors.

Which browser are you using? (if relevant)

Chrome 112.0.5615.138

How are you deploying your application? (if relevant)

Vercel

[ony3000]

I'm sorry for creating the same issue as facebook/react#26750, but it's an error that occurred in the process of creating the next application, so I'm reporting it to both sides.

[JesseKoldewijn]

Hey man!
Gonna be honest, haven't encountered this issue myself yet. I'll have a look on your error-reporting branch when I get home to see if I can find what is going on here. 👍

[nextjs-bot]

This issue has been automatically marked as stale due to two years of inactivity. It will be closed in 7 days unless there’s further input. If you believe this issue is still relevant, please leave a comment or provide updated details. Thank you.

[nextjs-bot]

This issue has been automatically closed due to two years of inactivity. If you’re still experiencing a similar problem or have additional details to share, please open a new issue following our current issue template. Your updated report helps us investigate and address concerns more efficiently. Thank you for your understanding!

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