Draft.js VS slate

Draft JS

Draft-js developed by Facebook, last update was over 2 years ago and it still got over 800k weekly downloads. I can't quite get it to work so I'm wondering if theres other good alternatives out there.

If you want to write the GUI code in Rust, you'd need something like Dioxus (which uses Tauri under the hood). But note that the Rust GUI ecosystem is still new, so I doubt we have something like Draft.js (a wysiwyg editor component for React). There's a lot of complexity involved in writing a text editor, and I'll suspect you'll have to handle a lot of that yourself.

How does this compare to Draft.js, another rich text editor created by Facebook?

https://draftjs.org/

FWIW, we updated the README to reflect the status of DraftJS today.

https://github.com/facebook/draft-js

Point taken about updating the site, though.

I think it would be helpful to explicitly say that draft.js is deprecated here [1]. I was recently caught out by this, and started using draft.js without realising it’s been abandoned.

1. https://draftjs.org/

>Sure, but indicate that it's an alpha product

Do you mean something like the banner on the README?

https://github.com/facebook/lexical

>They don't even have the decency to label it is such

Do you mean something like the big banner on the README?

https://github.com/facebook/draft-js

Draft-js. It is a JavaScript rich text editor framework, built for React and backed by an immutable model. Here is a link to it: https://draftjs.org

- it creates a layout based on rows and cells, so it support multi-column layout - each cell can contain a different "cell-plugin", - richt-text editor based on https://github.com/ianstormtaylor/slate is built in and comes with its own plugin system. It can do weight, italic, block-types, alignment and lists and can be extended as you want (even with elements storing data and interactive components) - you can create custom cell plugins based on a schema (or custom control ui) and a component that should be rendered - it stores an object tree that represent it, not html. It therefore can contain any react component, which is great if you want to allow your editors to add interactive components or components that you already built as part of the app - i carefully optimized for SSR and bundle size, so no editor ui is rendered nor loaded. editor ui is only loaded on the client if you disable readOnly. (lazy loading) - it mainly tested with nextjs, since i used it for content-heavy pages. - its not yet tested with react-server components, but it should actually work in read-only mode

Finally there's Slate and Lexical which are super powerful in terms of customizability and extensibility. They're great options for when the editing experience plays a major role in the product.

Slate, as per its documentation, is a completely customizable framework for building rich text editors. Therefore, it doesn't offer a feature-rich text editor but instead provides tools to build one. Let's create a component called Slate and see what the Slate editor looks like.

Link to Repo

Word of warning about Slate: I love the API and the design goals, but it appears to suffer from some fundamental issues. We were experiencing issues similar to this one and a team of multiple 10+ year experienced frontend devs couildn't figure out what was going on. I had to completely rip out a feature we had built with Slate and had to reimplement a new version from scratch with Lexical. So far we have no issues other than those inherent to rich text editing.

We're trying to choose between Lexical and Slate at work. Do you have any examples that would be similar to this? https://github.com/ianstormtaylor/slate/blob/main/site/examp...

If you are going to customise a ton of functionalities and/or implement new functionality I suggest using SlateJS. If not, have a look at Sun editor.

You definitely need to give Slate (https://github.com/ianstormtaylor/slate) a try - the best editor framework I've used.

Slate: Looks very promising, but it's for React. (Someone has floated the idea of making it framework-agnostic, but the maintainers haven't committed to that goal yet.)