Don't use react-quill with Next.js; you'll face a bunch of troubles.

[maykon-oliveira]

Thanks for filing an issue!

If at all possible, please provide a Codesandbox or Codepen to demonstrate the problem you're having with React Quill. Here's a template to get you started.

⚠️ Make sure that your bug hasn't already been fixed by ReactQuill v2.0.0-beta.2. See the homepage for instructions on how to upgrade.

Ticket due diligence

• [ ] I have verified that the issue persists under ReactQuill v2.0.0-beta.2
• [ ] I can't use the beta version for other reasons

ReactQuill version

• [ ] master
• [ ] v2.0.0-beta.2
• [ ] v2.0.0-beta.1
• [ ] 1.3.5
• [ ] 1.3.4 or older
• [ ] Other (fork)

FAQ

Is this a bug in Quill or ReactQuill?

ReactQuill is just a ~thin~ wrapper on top of the Quill editor. Often, what looks like a bug in ReactQuill, is actually a bug in the Quill editor itself. Before opening a ticket, please check the Quill documentation, and the issues page, and see if that answers your question first.

How do I access the wrapped Quill instance?

See the instance methods and API documentation.

[frdomovic]

@maykon-oliveira NextJS, is issue with not being able to disable and add binding to Enter key fixed?

[alexkrolick]

See https://github.com/zenoamaro/react-quill/issues/919

[maykon-oliveira]

@maykon-oliveira NextJS, is issue with not being able to disable and add binding to Enter key fixed?

Running F5 on the page, I'm getting this error. The component is a client component.

Edit.:

But, with if (typeof window !== "undefined" && !document) return <textarea id="editor-fallback" /> works.