Skip to content

Update dependency slate-react to v0.147.6 - #786

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/slate-react-0.x
Open

renovate[bot] wants to merge 1 commit into
mainfrom
renovate/slate-react-0.x

Conversation

@renovate

@renovate renovate Bot commented Nov 6, 2026 •

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Adoption Passing Confidence Diffend
slate-react ^0.125.0 → ^0.125.0 || ^0.147.0 age adoption passing confidence Diff
slate-react ^0.125.1 → ^0.147.6 age adoption passing confidence Diff

Release Notes

ianstormtaylor/slate (slate-react)

v0.147.6

Compare Source

Patch 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.

v0.147.5

Compare Source

Patch Changes
  • #​6358 a25994b Thanks @​dylans! - On Android, a keyboard correction whose target range points outside the editor now replaces the word before the caret instead of inserting the corrected word after it

v0.147.3

Compare Source

Patch Changes
  • #​6346 b34e312 Thanks @​dylans! - Firefox for Android no longer splits a word across blocks when a keyboard suggestion is accepted in an empty paragraph. Firefox commits the word as one insertText per character at offsets it computed first; once the first character re-rendered the empty leaf, the rest of the word went into the next block. A character that arrives within 25 ms of the previous one and targets somewhere other than the editor's selection is now inserted at the selection instead (#​6343).

v0.147.2

Compare Source

Patch Changes
  • #​6344 18f1927 Thanks @​dylans! - Chrome's Writing Direction menu command no longer breaks the editor. The command changes the DOM without a beforeinput event, wrapping text in a direction span, so React later threw NotFoundError on removeChild and the editor unmounted. Slate now undoes the DOM changes of any format* input it was not asked to handle first and keeps the selection.

v0.147.1

Compare Source

Patch Changes
  • #​6340 ca37117 Thanks @​dylans! - Report an element whose renderElement didn't render its children through editor.onDOMError when it mounts, naming the element's type and path. Before, nothing was reported, and lookups into the element returned null with no hint why.

v0.147.0

Compare Source

Minor Changes
  • #​6338 6c4cab5 Thanks @​dylans! - Add resolveDOMNode, resolveSlateNode, resolveSlatePoint and resolveSlateRange, which return null instead of throwing, like resolveDOMPoint and resolveDOMRange. Unlike suppressThrow: true, resolveSlatePoint and resolveSlateRange also return null before Editable mounts and for a selection with no range. The to lookups and suppressThrow are unchanged.

v0.146.1

Compare Source

Patch Changes
  • #​6334 0f99057 Thanks @​dylans! - resolveDOMPoint and resolveDOMRange no longer report a miss through editor.onDOMError. A miss is often ordinary: a layout effect that measures the selection runs before the edited text's DOM is attached, and replacing editor.children can leave the selection past the end of the new text, so these were reported as broken rendering when nothing was wrong. Slate no longer calls editor.onDOMError itself; the hook stays for apps and plugins.

    resolveDOMRange also returns null instead of throwing when the editor's window isn't registered yet, for example from a layout effect inside the first render, and checks the focus only when the anchor resolves. Scrolling the selection into view no longer throws when the unhung range ends in an element that doesn't render its children.

v0.145.1

Compare Source

Patch Changes
  • #​6329 3d7b2fa Thanks @​dylans! - A click inside the editor whose handler changes the clicked node, for example a <select> that calls setNodes on its element or a suggestion that inserts text, no longer throws "Unable to find the path for Slate node". Editable's click handling now returns when the clicked node is no longer in the document, which its existing check intended but findPath started throwing before it since 0.142.

v0.145.0

Compare Source

Minor Changes
  • #​6327 89a74de Thanks @​dylans! - Add a controlled value prop to Slate. Pass the value from onValueChange back in, and Slate recognizes that exact object and doesn't apply it again. Any other value is applied as a change from outside the editor through editor.setChildren, in a layout effect, so the selection and history stay valid. Values passed in aren't reported through onValueChange. Updates wait while the user is composing text or Android has pending input, and only the latest is applied. value and initialValue together throw.
Patch Changes
  • #​6325 6cb0eb4 Thanks @​dylans! - A DOM selection change made just before the editor loses focus now reaches editor.selection. Selection changes are processed a little later than they happen, and since 0.142 changes processed after blur were ignored, so for example clicking an element whose handler blurs the editor could leave editor.selection where it was before the click. Blur now processes any pending selection change first.

v0.142.0

Compare Source

Minor Changes
  • #​6316 342facf Thanks @​dylans! - createEditor takes an optional type parameter. createEditor() still returns Editor; createEditor<BaseEditor>() returns a plain BaseEditor, so a plugin chain is type-checked against the plugins actually applied rather than the fully extended CustomTypes editor.

v0.141.0

Compare Source

Minor Changes
  • #​6311 a1852f8 Thanks @​dylans! - Add opt-in inlineEdgeAffinity and leafEdgeAffinity editor hooks and Editor.insertionPoint for consistent insertion at inline and mark boundaries. Implicit text, fragment and inline-node insertion at collapsed carets follows the configured rules, and Editor.marks reports the receiving leaf’s marks. Both hooks default to null, preserving existing behavior.

    BaseEditor now requires the two affinity hooks and the insertionPoint query. Editors created through createEditor receive them automatically; structurally constructed editors and editor mocks must supply them. Slate React disables native insertion when affinity changes the receiving point, while retaining compatibility with older supported Slate peers that lack the helper.

    Committed Android typing that changes receiving leaves uses the existing action reconciliation path, so a native mutation does not remain rendered in the old leaf. Active composition retains its existing diff path.

  • #​6310 407a066 Thanks @​dylans! - Add a filter option to insertFragment. It is called for each node in the fragment with the destination block entry and returns false to skip that node.

Patch Changes
  • #​5937 428fd70 Thanks @​kinaluo! - insertFragment now splits the block when block-level nodes such as a void image are pasted mid-block, so they land between the two halves instead of above the block, and the cursor moves to the start of the second half. Dropping a dragged block void onto the middle of a paragraph splits it the same way. Schemas that don't allow blocks inside a structure (for example a list item's text wrapper) should override insertFragment to move those nodes elsewhere before calling the original.

v0.140.1

Compare Source

Patch Changes
  • #​6084 dcae734 Thanks @​a-y-ibrahim! - Keep the DOM and Slate value in sync when an insertText override rejects native text input, including insertions at decoration boundaries.

v0.140.0

Compare Source

Patch Changes
  • #​6105 a07df52 Thanks @​janpaepke! - Stop drops from throwing when the browser resolves the drop position outside of the editor. <Editable> resolved the target range from the drop coordinates via caretRangeFromPoint, which can land on a DOM node outside of the editor even though the event's target is inside it (e.g. when the page scrolled between the last dragover and the drop); the resulting "Cannot resolve a Slate point from DOM point" error escaped the event handler and the drop was lost. The dropped data now goes to the current selection instead (the end of the document without one), and internally dragged content stays where it is. DOMEditor.findEventRange gained a suppressThrow option for this and returns null when the range cannot be resolved.

  • #​6306 c4c990e Thanks @​dylans! - Expose the placeholder to assistive technology as aria-placeholder on the editor root while it is shown, and mark the visual placeholder aria-hidden so it isn't read as content.

v0.138.3

Compare Source

Patch Changes
  • #​6295 2d2a520 Thanks @​dylans! - Restore an existing editor selection when Tab or Shift+Tab focuses Editable. Keep the browser's initial placement when no selection exists, and preserve mouse-based caret placement.

  • #​6294 acca98f Thanks @​dylans! - Call caller-provided Editable event handlers in read-only mode while skipping Slate's editing behavior. Read-only editors remain outside the tab order unless a tabIndex is provided.

  • #​6290 ee31c77 Thanks @​dylans! - Accept undefined explicitly in the optional Editable, Slate, useSelected and createHyperscript options, so their published types stay compatible with exactOptionalPropertyTypes after the TypeScript 6 upgrade.

v0.138.1

Compare Source

Patch Changes
  • #​6287 b0462a1 Thanks @​dylans! - Limit whole-block deletion of a hanging selection, and native triple-click selections, to top-level blocks. Nested blocks such as table cells and list items keep the previous behavior, so cutting or dragging across cells in editors without editor.isIsolated no longer removes cells. After undoing a whole-block deletion, the default scrollSelectionIntoView scrolls to the restored text instead of the start of the following block.

v0.138.0

Compare Source

Patch Changes
  • #​6280 b397417 Thanks @​dylans! - Call scrollSelectionIntoView when keyboard navigation moves a selection already synchronized with the DOM, including native movement between text lines. Custom callbacks can keep the caret clear of sticky headers. Renders and edits without user input remain excluded from this additional scrolling path.

  • #​6282 f64a47f Thanks @​dylans! - Keep the browser's native triple-click selection outside editor.isIsolated elements, so Backspace and cut after a triple-click in Chrome and Safari remove the whole block as in a plain contenteditable. Inside isolated elements, triple-click still selects only the current block's contents. Firefox keeps its native non-hanging selection.

  • #​6279 dabbab7 Thanks @​dylans! - Use native selection word boundaries for word-navigation shortcuts so Option/Ctrl+Arrow respects native punctuation and language boundaries while synchronizing Slate's selection in the same key event. Fall back to Slate's word transform when native selection movement is unavailable.

v0.136.0

Compare Source

Minor Changes
  • #​6268 1e9e7e1 Thanks @​dylans! - Add Editor.word, which returns the range of the word around a point within its block. Words can cross mark changes and inline links but stop at voids, and isWordCharacter lets you define your own word characters. ReactEditor.getWord also includes text an input method is still composing.

    The 'word' unit (word deletion, word movement, and Editor.before/after/positions) now uses Intl.Segmenter, where available, to split runs of word characters. Chinese, Japanese and Thai text without spaces now deletes and moves one word at a time instead of a whole phrase. Text with spaces between words is unaffected.

v0.134.1

Compare Source

Patch Changes
  • #​6258 d5b2fbd Thanks @​nabbydude! - Speed up tree-altering operations by using faster array functions when copying and replacing children.

v0.134.0

Compare Source

Patch Changes
  • #​6250 b70a400 Thanks @​dylans! - Fix typing on Android right after toggling a mark with a collapsed selection. The first letter no longer moves the caret past the end of the previous leaf, which closed the soft keyboard and scattered the following letters, and a composition into the new marked text is no longer interrupted by a re-render.

  • #​6248 f9b0cbf Thanks @​dylans! - Fix an Android crash ("Failed to execute 'removeChild' on 'Node'") when typing starts in an empty editor just as the placeholder appears. The DOM restore that runs before Android renders no longer undoes React's own placeholder changes.

  • #​6243 56aa3c4 Thanks @​dylans! - Remove the source void when it is dragged to a new position, preventing duplicate voids when the dragged selection is collapsed.

  • #​6249 d879fc1 Thanks @​dylans! - Fix composed text appearing twice in Chrome when the caret sits at the start of a leaf that follows marked text. Chrome composes into the end of the previous leaf, so its copy is removed before Slate inserts the text into the selected leaf.

  • #​6251 927c228 Thanks @​dylans! - Remove text an IME composes into a selected void element. Slate doesn't insert text into voids, so the browser's copy was left in the void's DOM.

v0.133.8

Compare Source

Patch Changes
  • #​6238 468b58d Thanks @​dylans! - Scroll the caret into view when an edit changes the selection even if the DOM selection already matches the editor, including Backspace between empty paragraphs.

  • #​6235 22ede7f Thanks @​dylans! - Move the caret into an adjacent empty text node when an arrow key leaves an editable inline, so padding does not leave the caret drawn inside the inline.

v0.133.7

Compare Source

Patch Changes
  • #​6233 a0bcf70 Thanks @​dylans! - Sync the selection from the DOM before calling an Editable onClick handler, so editor.selection in the handler reflects the click instead of the previous selection.

v0.133.6

Compare Source

Patch Changes
  • #​6229 c486bad Thanks @​dylans! - Move the caret to the empty last line of a block that ends with a newline when pressing ArrowUp from the block below in Chrome and Safari, which skipped that block natively.

  • #​6226 a8329a2 Thanks @​dylans! - Copy initialValue nodes that another editor is already using, so two Slate components given the same value render and edit independently instead of throwing "Unable to find the path for Slate node". Requires slate-dom 0.133.6 or newer.

  • #​6225 cb788f8 Thanks @​dylans! - Extend the selection from a selected void when Shift-clicking text, instead of leaving it collapsed in the void in Chromium.

v0.133.5

Compare Source

Patch Changes
  • #​6224 84f047c Thanks @​dylans! - Replace an expanded selection correctly when an IME composition starts right after selecting it. The selection is now synced before the composition starts, and Firefox no longer crashes or leaves the replaced text in the document.

  • #​6222 c333eed Thanks @​dylans! - Render an empty block right-to-left when the nearest sibling block with text is right-to-left, so a new line after Hebrew or Arabic text starts on the right.

  • #​6220 3eed905 Thanks @​dylans! - Keep input, selection and history events from native contenteditable regions nested inside non-editable containers out of the surrounding Slate editor. Preserve Slate text and event hosts inside custom editable islands.

  • #​6223 8c929a8 Thanks @​dylans! - Keep the Firefox caret on the new line after a trailing soft break without adding zero-width characters to the document. Preserve selection offsets and copied text around the extra rendering newline.

    Requires slate-dom 0.133.5 or newer for the matching DOM selection mapping.

  • #​6219 8e8cf36 Thanks @​dylans! - Stop re-rendering every text node in a block when only one of them changes. Text and leaf components now compare what they use from the parent (its properties, whether the text is its last child, and whether the block is empty) instead of the parent object itself.

  • #​6221 270a4a0 Thanks @​dylans! - Call deletion overrides in WebKit when Backspace at the start or Delete at the end of a document does not emit beforeinput.

v0.133.4

Compare Source

Patch Changes
  • #​6215 ce3faf8 Thanks @​dylans! - Read the DOM selection when a beforeinput event arrives, so input that follows a selection change before the browser fires selectionchange goes where the caret is.

v0.133.3

Compare Source

Patch Changes
  • #​6212 e86bcd3 Thanks @​dylans! - Strip Babel's __self and __source development metadata from hyperscript attributes so generated documents remain serializable and do not contain local source paths.

v0.133.2

Compare Source

Patch Changes
  • #​5985 5eeea5e Thanks @​wljray! - Flush Android backward text deletions without waiting for another input event, retain the typing delay when no action is pending, cancel superseded flush timers, and avoid an extra change notification when restoring unchanged marks.

  • #​6207 906eafe Thanks @​dylans! - Restore Chromium's structural DOM changes before applying multiline composition commits, preventing duplicated text while preserving intervening React updates.

v0.133.0

Compare Source

Minor Changes

v0.132.0

Compare Source

Minor Changes
  • #​6187 d8cdecd Thanks @​dylans! - Add Range.direction(range), which returns 'forward', 'backward' or 'collapsed'. Range.isForward and Range.isBackward are unchanged; a collapsed range still counts as forward, which is now documented.
Patch Changes
  • #​6137 63134d0 Thanks @​cpruijsen! - Fix the PropsMerge type for Transforms.setNodes so the merge option can return scalar property values, not just objects.

v0.131.0

Compare Source

Minor Changes
  • #​6173 7850c31 Thanks @​dylans! - Transforms.wrapNodes and Transforms.unwrapNodes now unhang a range by default and accept hanging, like setNodes, insertNodes, mergeNodes and removeNodes. A selection that ends at the start of the next block no longer wraps or unwraps that block. Pass hanging: true to keep the old behavior.
Patch Changes
  • #​6177 fdc3dac Thanks @​dylans! - Only refill an emptied editor when a delete runs at the selection. In 0.130, Transforms.delete(editor, { at: path }) also inserted an untyped empty block when it removed the last node, which left an extra block behind in code that deletes every block and then inserts new content. Programmatic deletes with an explicit at now act like removeNodes again.

  • #​6176 22cf872 Thanks @​dylans! - Fix insertFragment into an editor whose only block is empty, which left an extra untyped empty block before the inserted content (a regression in 0.130).

  • #​6181 ec75af0 Thanks @​dylans! - Backspace at the start of a block that follows a list or table no longer pulls that block into the list or table. An empty previous block is now only removed in place of the merge when it's a sibling; otherwise the block merges into it as usual.

v0.130.2

Compare Source

Patch Changes
  • #​6171 7843bd5 Thanks @​dylans! - Moving whole lines by dragging or cutting no longer adds an empty line. Whole top-level blocks are now moved as blocks. Nested content, like list items and table cells, is moved without its trailing line break, so no containers get merged. Dropping text back onto its own selection is now a no-op, and drag-and-drop deletes through editor.deleteFragment, like cut does, so plugins that guard deletion apply to both.

v0.130.1

Compare Source

Patch Changes
  • #​6165 4a96e69 Thanks @​dylans! - Make Node.fragment only walk the top-level blocks the range covers, so copying or cutting in a large document no longer takes time proportional to the whole document.

v0.130.0

Compare Source

Minor Changes
  • #​6158 c760f06 Thanks @​dylans! - Deleting the only node in the editor, such as a lone image, now leaves an empty block instead of an editor with no children. An empty editor had no start point, so focusing or typing threw "Cannot get the start point in the node at path [] because it has no start text node".

v0.129.0

Compare Source

Minor Changes
  • #​6141 1604e5f Thanks @​dylans! - Deleting a character or word from an empty block next to a block void now removes the empty block and selects the void, instead of deleting the void. This matches native editors. The previous behaviour deleted the image when pressing Backspace in an empty paragraph after it.
Patch Changes
  • #​6132 ff63fad Thanks @​dylans! - Deleting a single character next to, or inside, an empty non-void inline now removes the inline, instead of skipping over it and deleting the character on its other side.

v0.128.0

Compare Source

Patch Changes
  • #​6115 52f05bf8 Thanks @​giaBaoJS! - - When deleting a void element backward from a cursor inside it, place the cursor before the removed void instead of moving it into the following node

    • In Chrome and Safari, pressing Delete on a selected void now deletes forward instead of backward
  • #​6003 50cdf5e9 Thanks @​nabbydude! - Changed type signature of Editor#setSelection to allow non-Range properties of Selections (functionality unchanged)

v0.127.1

Compare Source

Patch Changes
  • #​6110 fbe8e50b Thanks @​unrevised6419! - Declare @types/react (>=18.0.0) and @types/lodash (^4.14.0) as optional peer dependencies. The shipped type declarations import from react and lodash in type positions, but the typings packages were only listed in devDependencies. Under a hoisted node_modules layout that resolves by accident; under pnpm's isolated linker with a global virtual store it does not, and consumers get TS7016 implicit-any errors (or silently degraded any props) for the editor components. Both entries are optional, so JavaScript-only consumers do not get unmet-peer warnings.

v0.126.4

Compare Source

Patch Changes
  • #​6099 ad04f91c Thanks @​BetterAndBetterII! - Skip Selection.collapseToEnd() during composition selection-sync when the live DOM selection has no ranges, so a cleared selection no longer throws InvalidStateError and unmounts the editor.

v0.126.3

Compare Source

Patch Changes
  • #​6096 b96028a5 Thanks @​melodysdreamj! - Fix IME composition being cancelled on the first character typed into an empty leaf on Android, which left the first character behind as a separate, uncomposed character (typing 안녕 in Korean produced ㅇ안녕).

v0.126.0

Compare Source

Patch Changes
  • #​6074 c5ea32ea Thanks @​greymoth-jp! - Treat Indic conjunct clusters as a single grapheme in getCharacterDistance, implementing Unicode UAX #​29 rule GB9c. Character-by-character cursor movement (Editor.positions with unit: 'character', and the Editor.before / Editor.after it powers) over scripts such as Devanagari and Bengali no longer stops inside a Consonant + virama + Consonant conjunct.

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate Bot added the dependencies This updates dependency files label Nov 7, 2026
@github-actions

github-actions Bot commented Nov 7, 2026 •

Copy link
Copy Markdown
Contributor

GitLab Pipeline Action

General information

Link to pipeline: https://gitlab.com/code0-tech/development/pictor/-/pipelines/3085839690

Status: Passed
Duration: 5 minutes

Job summaries

storybook:build

Storybook available at https://code0-tech.gitlab.io/-/development/pictor/-/jobs/18157970158/artifacts/storybook-static/index.html

@renovate
renovate Bot force-pushed the renovate/slate-react-0.x branch from 5cd317f to 7a6650c Compare November 11, 2026 18:32
@renovate
renovate Bot force-pushed the renovate/slate-react-0.x branch from 7a6650c to 6413784 Compare November 18, 2026 19:08
@renovate renovate Bot changed the title Update dependency slate-react to v0.147.5 Update dependency slate-react to v0.147.6 Nov 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies This updates dependency files

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant