Error: Cannot resolve a DOM node from Slate node

[gbozzetti]

Description

Hello,

I followed all the steps in the guide to create a Basic Editor with Basic Marks, and everything works as expected.

The only issue is that every time I click on a button in the toolbar, I see an error message in the console (even though everything works):

Uncaught Error: Cannot resolve a DOM node from Slate node: {"children":[{"type":"p","children":[{"text":"Hello","bold":true},{"text":"! Try out the "},{"text":"bold","bold":true},{"text":", "},

Can you explain me what is going on here?

Thank you!

Reproduction URL

No response

Reproduction steps

1. Go to Plate guide
2. Follow all the steps to install Vite React + ts, shadcn/ui, Plate UI
3. Install the components as described in the guide
4. Copy/Paste the code from the guide related to Basic Mark example

Plate version

49.2.3

Slate React version

not using

Screenshots

Logs

Browsers

Chrome

[dosubot]

Hi @gbozzetti! I'm Dosu and I’m helping the plate team.

This error happens when Plate tries to map a Slate node to a DOM node, but the mapping fails—usually because the node isn’t rendered, the selection is on a void/inline node, or the DOM mapping is briefly out of sync. It’s a “soft” error: the editor keeps working, but the console logs a warning.

Recent Plate updates fixed bugs in how DOM nodes are resolved for selections, especially for edge cases like partial selections or void nodes. These fixes landed in PRs #4463 and #4465. If you’re on Plate 49.2.3 and still seeing this, double-check that you don’t have any custom toolbar or selection logic that might reference a node that isn’t rendered. If you do, add a check to make sure the node exists before trying to resolve its DOM node—for example, only call editor.api.toDOMNode(node) if node is defined and rendered.

If you’re using the latest Plate and the error persists, it’s safe to ignore unless it’s breaking your workflow. If you want to dig deeper, sharing your exact code or checking for customizations around toolbar actions and selection handling could help pinpoint the cause.

References:
getSelectedDomFragment fixes
void/inline node handling
Defensive checks discussion

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}    

[Hakaze]

It's actually a dependency issue, 2 different versions of the following packages, i resolved it by setting overrides in package.json.

  "overrides": {
    "slate": "0.118.0",
    "slate-dom": "0.117.4",
    "slate-react": "0.117.1"
  }