Lexical - the Hot New JS Rich Text Editor 🔥

[@Dadylongarms]

I was really getting ready to dig into Slate and decided to look up what else? And you video popped up. Thank You!!

[@EdgarManukyan]

Thanks so much for this. I think you made the first video on Lexical :) We also need nice tutorials since the documentation is pretty scarce.

[@CODE_IS_EVERYTHING]

Absolutely. I’m excited to watch Lexical’s growth, it is looking very promising.

[@shafiemukhre]

I'm trying to see what are some of the rich text editor library and this is great content. I also appreciate that your shared other available libraries and your personal recommendation

[@Giregg]

I agree with you, Slate can get the job done, but damn it's a horrible developer experience 😂

[@bonekolekta]

Very cool review. Are you going to do another one soon?

[@haskup]

You made my day thank you sir

[@ufucuk]

This channel has so much future potential, just sayin!

[@CODE_IS_EVERYTHING]

I appreciate you saying that.

[@irfansaeedkhan7242]

do you have any working crud operation link plz ?

[@Giregg]

Please make some tutorials on lexical, because the documentation is non-existant right now haha

[@CODE_IS_EVERYTHING]

Hey, I’ll definitely consider it

[@JoshuaAngelo]

@@CODE_IS_EVERYTHING Please. Right now it is just pain to try and figure out. Even trying to understand it on the discord is hard because I am getting told that the function to serialize the data and read it doesn't work but the work around is using a callback that isn't react related and there is no documentation regarding it.

[@CODE_IS_EVERYTHING]

@@JoshuaAngelo Hey, I'd recommend using Tiptap if you're trying to build something for any sort of production usage right now. I was playing around with Lexical to see if I could get to the point making a tutorial on it, but I too encountered many issues. I'll have a video up in a day or two on Tiptap. Lexical is an exciting development, but I think it is too early to adopt it for a serious project at the moment unless you're wanting to contribute to the project itself and really understand how it works. If you're just trying to get a working component (like me), I think something more stable is the move.

[@donner7708]

@@CODE_IS_EVERYTHING thank you that's really good information. I have been looking everywhere for one that is up to date but I have had terrible luck. I'll try out your recommendation!

[@pacman358]

How did you make the toolbar?

[@JH-br4iv]

Solid video! thanks!

[@CODE_IS_EVERYTHING]

Thanks! Glad you liked it.

[@yousefsaeed732]

After the user submit the form how can i store the mark down ?

[@DnKZone]

Exactly....not documented in the documentation...

[@amitabhkumar2677]

1:49

[@adtc]

I came here because after looking at Slate for 3 days, I can't figure out a single sht in it. It's FRUSTRATING! Even their examples are horribly coded. And I'm usually quite good at figuring out complex problems, so IDK. Also their Docs are really really bad. There's very little mentioned about the API.

[@CODE_IS_EVERYTHING]

I feel that pain. I built an app a few years ago that was heavily built on slate because there weren’t many options and it was not enjoyable. If you are wanting to use slate and you’re using react you might want to take a look at this: github.com/udecode/plate. Looks like a nice wrapper over slate.