lexical

You are wrong, Lexical it is not in maintenance mode and continues to receive commits from contributors. 24k stars and counting. https://github.com/facebook/lexical

Seems like the contribution graph is on the highest for long time: https://github.com/facebook/lexical/graphs/contributors?from... But Claude is playing part of it.

I would be curios that what are the cons/pros for selecting this over Facebook's Lexical (https://github.com/facebook/lexical)

>If you are doing something remotely non-trivial, you will need the customization that only ProseMirror provides, and you will learn that the hard way. As far as I know Meta's Lexical [1] (used by Facebook, Whatsapp, and Instagram) is goes also a similar direction: customizable, but it takes time to get used to it. [1] https://github.com/facebook/lexical

We are using this at work. Generally I'm pretty happy with the configuration driven approach. You have config objects for all your collections where you define the types of the fields and everything else happens automatically. With this comes a few gotchas. It's easy for an unassuming developer to change the name of a field (e.g., upper to lower case) and suddenly all data is gone in production since this affects the database. What you should do instead is write a migration. I'm also not a fan of Lexical. It's very focused on being a good rich text editor but not on being a good document format for your clients. For example the way they render lists is, in my opinion, simply wrong (see https://github.com/facebook/lexical/issues/2951). Or this https://github.com/facebook/lexical/issues/6269. You also have the added complication of using th

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?

For a text editor, Lexical looks promising https://github.com/facebook/lexical

Indeed, it seems that copy-pasted playground with custom UI. They didn't bother themselves even to create at least some new plugin for it. Playground plugin: https://github.com/facebook/lexical/blob/main/packages/lexic... Copy paste: https://github.com/ozanyurtsever/verbum/blob/bfac38815eb0057... Made a PR at least to credit the authors https://github.com/ozanyurtsever/verbum/pull/3/files

Yes, we have something like this in @lexical/selection: https://github.com/facebook/lexical/blob/af099ffd9f464b523d6...

It is interesting (and cool) that this uses Typescript over Flow. It seems like Flow is still being developed too. Just looking at the top level package.json [1], I wonder at which point you abstract all those copy/pasted targets into a script that takes an argument. [1] https://github.com/facebook/lexical/blob/main/package.json#L...

https://github.com/facebook/lexical/blob/5802651c24d88b2f7d2... > // Check for any random auto-added <br> elements, and remove them. > // These get added by the browser when we undo the above mutations > // and this can lead to a broken UI. This made me laugh out loud. Browsers! Until here our approach looked quite similar. Leave the observer connected during reverts and avoiding double-peocessing using .takeRecords never occurred to me, I always disconnect it. Maybe some of these brs are causing chaos…

Yeah, I really wanted to avoid them too. There doesn't seem a good way. The issue you describe with selection jumping is a well known issue with GBoard. Here's the logic for the mutation handling: https://github.com/facebook/lexical/blob/main/packages/lexic...

I'd love to use Lexical to replace what we're using today. I've been checking in on the repository every few weeks. However, there are many features that are still pending https://github.com/facebook/lexical/projects/1 . We need several of the features that are "V1.0" and we obviously need the stability of a 1.0 SemVer release :) Is there a general timeline goal for the V1.0 release?

Android is indeed a headache to support. The biggest issue is how all keyboards force composition on all keystrokes, meaning you're constantly having to read the DOM input and work out what might have been entered. We don't use extra DOM nodes, but we do listen to `beforeinput`, `input` and use DOM MutationObserver to try and detect common Android patterns. I'd search this module for references to Android: https://github.com/facebook/lexical/blob/main/packages/lexic...