react-quill VS lexical

The email template settings page should provide a user interface where users can see and edit the email template. The react-quill (https://github.com/zenoamaro/react-quill) component will be used as the editor for the email template message.

Did you consider react quill instead of tiptap? If so, why did you choose it?

const rt = useRef(); const doAThing = useCallback(()=> { const editor: Quill = rt.getEditor(); // add a button to the toolbar here using // the api: https://github.com/zenoamaro/react-quill/tree/v1.3.5 }, [rt]);

i'm using react-quill.

To demonstrate how Quill works, we are going to use the React-Quill package, which is a React wrapper around the Quill editor. Below we have a component that will render the React Quill editor with a toolbar that offers tools for formatting text.

What I used is this one: https://www.npmjs.com/package/react-quill

I could dig into that and explain but it would probably be easier for you to just look at react-quill since it's already doing what you want.

I'm using this editor in a React application with PostgREST and PostgreSQL. I plan to store the RT in text fields. Looking for advice and cautions on whether this is a good approach.

Quill is also pretty nice.

Quill has good libraries but has completely fallen into disrepair across the board. ReactJS I would argue is in an even worse state.

I remember using https://github.com/facebook/lexical for a project a year ago and mostly things worked our of the box.

Any reason to prefer quill?

Lexical (https://lexical.dev/) is really nice to use and doesn't use Prosemirror or CKEditor.

I've tried to get to grips with Lexical but found the docs pretty hard to follow. It definitely seems to offer pretty heaps of power, just unlocking that seemed tricky. We're hoping to use it for customer facing collaborative list product that allows for richer media (video, code blocks etc.)

Yes, it uses the Lexical framework internally, so markdown gets converted to an AST, then the AST gets serialized back.

Rich text editing doesn't imply pagination. Contenteditable is not abandoned. Lexical[1], Meta's framework for text editing relies on contenteditables.

[1]: https://lexical.dev/

lexical is a framework for building web based text-editors ... so yea it can do formatting but if you are using it to just do formatting you are very much using the wrong tool.

Haven't tried it out myself, but it's probably Lexical.

Svelte just got a lot more interesting! Dominic who is the creator of LexicalJs and InfernoJs (which is known to be insanely fast) has joined the svelte core team and is now working at Vercel full time! Here is the announcement on Twitter!