[dependabot]

Bumps the js-minor-and-patch group with 5 updates:

Package	From	To
slate	0.126.2	0.130.1
slate-dom	0.126.0	0.130.1
slate-history	0.115.0	0.128.1
slate-react	0.127.1	0.130.2
@playwright/test	1.63.0	1.64.0

Updates slate from 0.126.2 to 0.130.1

Release notes

Sourced from slate's releases.

slate-dom@0.130.1

Patch Changes

• #6169 fa2fcd0 Thanks @​dylans! - Keep empty blocks as a <br> in copied HTML, so pasting into Word and other rich-text targets no longer drops empty lines.

slate-react@0.130.1

Patch Changes

• #6167 eb9dc9b Thanks @​dylans! - Add -webkit-user-select: none to the default placeholder style so iOS Safari can't partially select the placeholder text.

• #6166 a0bcfaa Thanks @​dylans! - Shift-clicking a void element now extends the selection to it instead of collapsing the selection onto the void.

slate@0.130.1

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.

slate-dom@0.130.0

Patch Changes

• #6159 6b7a233 Thanks @​dylans! - Copy node objects passed to insertNodes that are already in a document, or that were inserted before, so each position gets its own object. Reusing an object, such as a template node inserted twice, made two nodes share one key and one parent entry, which broke rendering, selection and findPath. A node's first insertion keeps its object identity.

slate-react@0.130.0

Patch Changes

• #6164 209c334 Thanks @​dylans! - Fix typed text coming out reversed after a soft break at the end of a leaf in Chrome. Chrome reports the caret after a trailing \n as the start of the next text node, and Slate restored its own selection after each insert, so every character landed in front of the last.

slate@0.130.0

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

slate-hyperscript@0.129.1

Patch Changes

• #6152 fde516b Thanks @​dylans! - Type the tags added through createHyperscript's elements and creators options, so h('item') for a custom shorthand type-checks instead of failing with TS2345.

slate-dom@0.129.0

Minor Changes

• #6009 e885f88 Thanks @​gbalint! - Add DOMEditor.isMounted(editor) to check whether the editor has a DOM element, and use it in focus and hasDOMNode. hasDOMNode now returns false for an editor that is not mounted, instead of throwing.

... (truncated)

Commits

• d5222ae Version Packages (#6168)
• fa2fcd0 Keep empty blocks as a line break in copied HTML (#6169)
• fd40445 Correct the element check signatures and the serializing DOM Node (#6170)
• eb9dc9b Add the WebKit-prefixed user-select to the placeholder (#6167)
• a0bcfaa Extend the selection when shift-clicking a void (#6166)
• 4a96e69 Only walk the covered blocks in Node.fragment (#6165)
• a427bf1 Version Packages (#6163)
• 76bf4de Upgrade Babel to the latest 7.x (#6161)
• 209c334 Keep the caret moving when typing after a soft break in Chrome (#6164)
• 46f6d86 Document when Editable fires native input events (#6162)
• Additional commits viewable in compare view

Updates slate-dom from 0.126.0 to 0.130.1

Release notes

Sourced from slate-dom's releases.

slate-dom@0.130.1

Patch Changes

• #6169 fa2fcd0 Thanks @​dylans! - Keep empty blocks as a <br> in copied HTML, so pasting into Word and other rich-text targets no longer drops empty lines.

slate-dom@0.130.0

Patch Changes

• #6159 6b7a233 Thanks @​dylans! - Copy node objects passed to insertNodes that are already in a document, or that were inserted before, so each position gets its own object. Reusing an object, such as a template node inserted twice, made two nodes share one key and one parent entry, which broke rendering, selection and findPath. A node's first insertion keeps its object identity.

slate-dom@0.129.0

Minor Changes

• #6009 e885f88 Thanks @​gbalint! - Add DOMEditor.isMounted(editor) to check whether the editor has a DOM element, and use it in focus and hasDOMNode. hasDOMNode now returns false for an editor that is not mounted, instead of throwing.

Patch Changes

• #6139 b15d7dc Thanks @​dylans! - Keep the editor's selection when DOMEditor.focus is called with a void, such as a mention, selected. The DOM selection is now applied after focusing the editable, because Chromium resets a caret placed inside non-editable content when focus arrives afterwards.

• #6136 96ceedb Thanks @​dylans! - Keep a forward DOM selection that ends inside a block void when converting it with toSlateRange, instead of unhanging it to the end of the previous block.

• #6131 6c7c452 Thanks @​dylans! - Resolve drop positions inside shadow DOM. findEventRange passes the editor's shadow root to caretPositionFromPoint where the browser supports it, instead of resolving to the shadow host and throwing "Cannot resolve a Slate point from DOM point".

• #6138 eb25ecd Thanks @​dylans! - Only read data-slate-fragment from an HTML attribute when pasting, so pasted text that happens to contain data-slate-fragment="…" no longer makes the paste fail.

Commits

• d5222ae Version Packages (#6168)
• fa2fcd0 Keep empty blocks as a line break in copied HTML (#6169)
• fd40445 Correct the element check signatures and the serializing DOM Node (#6170)
• eb9dc9b Add the WebKit-prefixed user-select to the placeholder (#6167)
• a0bcfaa Extend the selection when shift-clicking a void (#6166)
• 4a96e69 Only walk the covered blocks in Node.fragment (#6165)
• a427bf1 Version Packages (#6163)
• 76bf4de Upgrade Babel to the latest 7.x (#6161)
• 209c334 Keep the caret moving when typing after a soft break in Chrome (#6164)
• 46f6d86 Document when Editable fires native input events (#6162)
• Additional commits viewable in compare view

Updates slate-history from 0.115.0 to 0.128.1

Release notes

Sourced from slate-history's releases.

slate-history@0.128.1

Patch Changes

• #6063 6ec6ab5c Thanks @​suyash-vyas! - Fix HistoryEditor.withMerging, HistoryEditor.withNewBatch and HistoryEditor.withoutMerging leaving the history flags corrupted when fn throws, and a nested withNewBatch that applies no operation clearing the pending split of the enclosing withNewBatch.

Commits

• a40f714 Version Packages (#6128)
• 4776b09 Stop deleteBackward('line') from throwing when the DOM can't be measured (#6055)
• 94aaf88 chore(deps): bump undici from 6.28.0 to 6.29.0 (#6125)
• e7a42c3 chore(deps-dev): bump shell-quote from 1.9.0 to 1.11.0 (#6126)
• 6ec6ab5 fix: HistoryEditor helpers leaving flags stuck when fn throws, and nested wit...
• c33a3dd Update the site to Next 15 (#6127)
• d096b39 Batch the Dependabot lockfile bumps that pass CI (#6124)
• 42bbbf4 Version Packages (#6122)
• d506c75 Mark the scripted-input changeset as minor, not major (#6123)
• 52f05bf Keep cursor before a void when deleting it backward (#6115)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for slate-history since your current version.

Updates slate-react from 0.127.1 to 0.130.2

Release notes

Sourced from slate-react's releases.

slate-react@0.130.2

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.

slate-react@0.130.1

Patch Changes

• #6167 eb9dc9b Thanks @​dylans! - Add -webkit-user-select: none to the default placeholder style so iOS Safari can't partially select the placeholder text.

• #6166 a0bcfaa Thanks @​dylans! - Shift-clicking a void element now extends the selection to it instead of collapsing the selection onto the void.

slate-react@0.130.0

Patch Changes

• #6164 209c334 Thanks @​dylans! - Fix typed text coming out reversed after a soft break at the end of a leaf in Chrome. Chrome reports the caret after a trailing \n as the start of the next text node, and Slate restored its own selection after each insert, so every character landed in front of the last.

slate-react@0.129.0

Patch Changes

• #6140 7119501 Thanks @​dylans! - Stop dropping Android input that arrives before the editor re-renders. When the node map was stale, beforeinput events were ignored, so the browser's native insert was overwritten by the next render. That lost the first character typed into an emptied editor, or every other character when typing fast. They now resolve against the editor's selection instead of the stale DOM.

• #6130 ab50c3b Thanks @​dylans! - Initialize the editor from initialValue when a different editor is passed to an already mounted <Slate>, such as when React fast refresh re-runs the useMemo that creates it. Previously the new editor kept empty children, and the next operation threw "Cannot find a descendant at path [0]".

slate-react@0.128.0

Minor Changes

• #6117 4e8cf0aa Thanks @​juliankrispel! - Ignore input, paste and drop events dispatched by script rather than by the user, so a script running on the page can no longer insert content without the user acting.

  This breaks tests that simulate a paste by dispatching an event, such as fireEvent.paste or Cypress's trigger('paste'). Drive a real paste instead, with Playwright's keyboard or cypress-real-events, or call editor.insertData directly.

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

Commits

• 978880c Version Packages (#6172)
• 7843bd5 Move whole lines as blocks when dragging or cutting (#6171)
• d5222ae Version Packages (#6168)
• fa2fcd0 Keep empty blocks as a line break in copied HTML (#6169)
• fd40445 Correct the element check signatures and the serializing DOM Node (#6170)
• eb9dc9b Add the WebKit-prefixed user-select to the placeholder (#6167)
• a0bcfaa Extend the selection when shift-clicking a void (#6166)
• 4a96e69 Only walk the covered blocks in Node.fragment (#6165)
• a427bf1 Version Packages (#6163)
• 76bf4de Upgrade Babel to the latest 7.x (#6161)
• Additional commits viewable in compare view

Updates @playwright/test from 1.63.0 to 1.64.0

Release notes

Sourced from @​playwright/test's releases.

v1.64.0

🧰 WebMCP

New page.webmcp and frame.webmcp give access to the tools that a page registers through the experimental WebMCP browser API, so you can test them like any other part of your app:

const browser = await chromium.launch({ args: ['--enable-features=WebMCP'] });
const page = await browser.newPage();
await page.goto('https://example.com');
for (const tool of await page.webmcp.tools())
console.log(tool.name, tool.description);
const result = await page.webmcp.callTool('add', { a: 2, b: 40 });
console.log(result.content[0].text); // "42"

Playwright MCP also supports WebMCP by default, with page-defined tools offered to the agent as webmcp_<tool>. Pass --no-webmcp to opt out.

playwright-cli exposes them as well:

playwright-cli webmcp-list
playwright-cli webmcp-call search_catalog --params '{"query":"cats"}'

🎬 Better videos

Videos can now be recorded at a custom frame rate, and the decorations for actions are styled with plain CSS:

// playwright.config.ts
import { defineConfig } from '@playwright/test';
export default defineConfig({
use: {
video: {
mode: 'on',
size: { width: 1920, height: 1080 },
fps: 60,
show: {
actions: {
style: {
point: 'width: 20px; height: 20px; border-radius: 50%; background: red',
highlight: 'outline: 2px solid #333; background: rgba(0, 128, 255, .15)',
title: 'font-size: 16px',
},
},
},
},
</tr></table>

... (truncated)

Commits

• 606ecd8 cherry-pick(#43192): fix(locators): parse locators the way the client API bui...
• e4f872c cherry-pick(#43188): feat(api): expose asLocatorDescription via LocalUtils fo...
• f6a439e cherry-pick(#43189): docs(webmcp): expose WebMCP to all languages
• e2335c3 cherry-pick(#43174): fix(mcp): do not close the browser twice when the client...
• d2a436e cherry-pick(#43163): Revert "fix(blob): do not remove existing reports from o...
• a0c4b5e cherry-pick(#43175): feat(api): return language-specific locator code from re...
• 3f7d535 cherry-pick(#43131): docs: fix broken C# samples in API docs and handles guide
• 1cde64f cherry-pick(#43170): fix(locators): parse mixed role options
• 8851e72 cherry-pick(#43171): fix(locators): parse JavaScript escapes and regex classes
• dcc5065 cherry-pick(#43172): fix(locator): parse within and getByRef locators
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[dependabot]

Looks like these dependencies are updatable in another way, so this is no longer needed.