[BUG] onChange does not fire with next.js >= 14.2

[MISTCLICK]

• [x] I have searched for similar issues in both open and closed tickets and cannot find a duplicate.
• [x] I have read the documentation and cannot find an answer.

Describe the bug After updating next.js to version 14.2 and later trying 14.2.1 the onChange function does not fire when the editor input changes. With next.js 14.1.4 the onChange function fires just fine.

Reproduction I am unfortunately unable to use codesandbox since any attempt to use it results in a complete system crash on my PC.

To Reproduce

1. Create an empty next.js app using create-next-app with next.js ^14.2
2. Follow the steps outlined in the docs to create a text editor (using headings, links, quotes and markdownShortcuts plugins).
3. Create an onChange function (e.g. console.log)
4. Make changes to the editor and observe no logs in the console

Expected behavior It is expected for the onChange function to fire every time that a change is made to the text editor.

Screenshots N/A

Desktop (please complete the following information):

• OS: Windows 11, Ubuntu 20 (server environments)
• Browser: Google Chrome (Win 11), Microsoft Edge (Win 11), Opera GX (Win 11), Safari (on mobile, iOS 17.4, iPhone 13).

Additional context N/A

[jonow]

I am having the same issue. It was working for me a few days ago, so I think it must be related to the recent update.

[petyosi]

Confirming that. Next.js 14.2.0 did something that altered Lexical's behavior. I contacted the Lexical team, with a reproduction here: https://github.com/mdx-editor/lexical-issue

Additional details - this is a problem only in dev mode.

[petyosi]

Opened an issue here: https://github.com/vercel/next.js/issues/64486

[github-actions[bot]]

:tada: This issue has been resolved in version 2.20.3 :tada:

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot :package::rocket:

[petyosi]

Updated the MDXEditor package to work around the change, now it works in https://github.com/mdx-editor/mdx-editor-in-next/commit/f5d2c7fecf413918442c4c11e975dac4f15b1ce0.

[MISTCLICK]

Thank you for the prompt reaction and resolution of this issue! <3

[imesse]

I'm still facing the issue in Next 14.2.4, with mdx editor v: "3.6.1".