next.js icon indicating copy to clipboard operation
next.js copied to clipboard

Next.js 14.2.0 changed facebook/lexical behavior in dev mode

Open petyosi opened this issue 1 year ago • 2 comments

Link to the code that reproduces this issue

https://github.com/mdx-editor/lexical-issue

To Reproduce

To reproduce, run the project and open the console. You will see:

binding counter 0
binding counter 1
Update listener from instance 0

Typing in the editor triggers updates from instance 0.

If you run

npm i [email protected]

And run the project again, you will see:

binding counter 0
binding counter 1
Update listener from instance 1

Typing in the editor triggers updates from instance 1.

Current vs. Expected behavior

The behavior of Next 14.1.1. The latest instance should be the one triggering changes.

Provide environment information

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.4.0: Fri Mar 15 00:12:41 PDT 2024; root:xnu-10063.101.17~1/RELEASE_ARM64_T8103
  Available memory (MB): 16384
  Available CPU cores: 8
Binaries:
  Node: 20.11.1
  npm: 10.2.4
  Yarn: 1.22.19
  pnpm: 8.15.5
Relevant Packages:
  next: 14.2.1-canary.5 // Latest available version is detected (14.2.1-canary.5).
  eslint-config-next: N/A
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.1.3
Next.js Config:
  output: N/A

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

Not sure

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

next dev (local)

Additional context

No response

petyosi avatar Apr 15 '24 06:04 petyosi

I encountered a very similar issue and posted a PR in https://github.com/facebook/lexical/pull/6271. Maybe you can try patching @liveblocks/react with similar changes?

meronogbai avatar Jun 12 '24 02:06 meronogbai

This issue has been automatically marked as stale due to 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 avatar Dec 09 '25 23:12 nextjs-bot

This issue has been automatically closed due to 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!

nextjs-bot avatar Dec 16 '25 23:12 nextjs-bot