ianstormtaylor /slate
A completely customizable framework for building rich text editors. (Currently in beta.)
★ 31,745⑂ 3,305👁 281⑃ 2,912● 3,251▤ 315
+0
日增长
-1
周增长
-2
月增长
31,745
stars
3,305
forks
281
watchers
2,912
prs
3,251
issues
315
releases
Top issues
#6343On Firefox for Android, autocompletion in a new paragraph behaves bizarrely4 comments · 2026-10-21#6038Perf: repeated tree updates need a batch-aware apply engine2 comments · 2026-03-31#6342`withReact()` is generic over `BaseEditor` instead of `Editor`1 comments · 2026-10-21#6360Focused <input> inside a void stops accepting text since slate-react 0.131 (#6184 snap-back)0 comments · 2026-10-29
Discussions
#6348Portable Slate core/history regression traces0 comments · 2026-10-25#5952Recommended ways to go about interaction testing1 comments · 2025-09-04#5879Slate-dom Peer Dependency1 comments · 2025-05-20#5858Is this approach to render the output a bad approach ?1 comments · 2025-05-02#5846Big shots, how to use code to update content without triggering onValueChange()? Similar events only occur when users manually modify it0 comments · 2025-04-21#5829SlateJS and folding1 comments · 2025-03-19#5816[Slate] editor is invalid!0 comments · 2025-03-07#5797The bold code in the Range.includes method seems redundant.1 comments · 2025-01-22
Latest release
[email protected] [email protected] 2026-11-11Patch Changes - 6364 6f00413 Thanks @dannelundqvist! - Copy and cut now use the selection the user just made. Selection changes reach editor.selection a little later than they happen, and copy and cut wrote the clipboard from editor.selection, so a copy straight after selecting, such as Ctrl+A followed at once by Ctrl+C, could copy the previous selection or nothing at all. Copy and cut now process any pending selection change first, before an onCopy or onCut handler runs.