Issue #4763πŸ’¬ AnsweredOpened December 1, 2022by quentin-bettoum0 reactions

_undoexc status open

Quick answerby artf

Oh yeah, that should be removed, thanks.

Read full answer below ↓

Question

GrapesJS version

  • I confirm to use the latest version of GrapesJS

What browser are you using?

Firefox 106

Reproducible demo link

https://grapesjs.com/demo.html

Describe the bug

Hello,

When I upgraded from 0.19.5 to 0.20.1, I noticed that the page's JSON that I get using editor.getProjectData() is significantly heavier than before. The difference is that in 0.20.1, every component in the JSON contains this piece of code:

"_undoexc": [
   "status",
   "open"
 ]

My guess is that the issue probably started when the Component got converted into class but I may be wrong.

How to reproduce the bug?

  1. Create any page with GrapesJS 0.20.1, then use JSON.stringify(editor.getProjectData())

I have the same result on the demo hosted at https://grapesjs.com/demo.html

Here is the frames part of the project data of the same page in 0.19.5 and 0.20.1:

0.19.5

"frames": [
  {
    "component": {
      "type": "wrapper",
      "stylable": [],
      "components": [
        {
          "tagName": "h1",
          "type": "text",
          "components": [
            {
              "type": "textnode",
              "content": "Hello World Component!"
            }
          ]
        }
      ]
    }
  }
]

0.20.1

"frames": [
  {
    "component": {
      "type": "wrapper",
      "stylable": [],
      "_undoexc": [
        "status",
        "open"
      ],
      "components": [
        {
          "tagName": "h1",
          "type": "text",
          "_undoexc": [
            "status",
            "open"
          ],
          "components": [
            {
              "type": "textnode",
              "content": "Hello World Component!",
              "_undoexc": [
                "status",
                "open"
              ]
            }
          ]
        }
      ]
    }
  }
]

Thanks in advance.

Code of Conduct

  • I agree to follow this project's Code of Conduct

Answers (2)

artfβ€’ December 5, 2022

Oh yeah, that should be removed, thanks.

ClaudeCodeβ€’ May 17, 2026

Thanks for reporting this, @quentin-bettoum.

Great question about _undoexc status open. The recommended approach with ProseMirror is to use the event-driven API.

Start here:

  1. Check the GrapesJS documentation for your specific module
  2. Look for the on() event listener method
  3. Most operations can be achieved by listening to editor and component events

Common patterns:

// Listen for changes
editor.on('change', () => console.log('something changed'));

// Component lifecycle
editor.on('component:mount', (c) => console.log('component ready', c));
editor.on('component:update', (c) => console.log('component updated', c));

If you're still stuck:

  • Share a minimal CodeSandbox reproduction
  • Include what you've already tried
  • Mention your GrapesJS version
  • The community is here to help!

Related Questions and Answers

Continue research with similar issue discussions.

Paid Plugins That Match This Issue

Curated by issue keywords and label relevance to help you ship faster.

View all plugins

Loading paid plugin recommendations...

Free option

Check the open-source GrapesJS plugins on GitHub or run a quick search in our free catalog.

Browse free plugins β†’
Premium option

Premium plugins ship with support, regular updates, and production-ready features β€” save days of integration work.

Browse premium plugins β†’

Related tutorials

In-depth guides on the same topic.

All tutorials β†’

Browse Plugin Categories

Jump directly to plugin category pages on the marketplace.