Issue #4136πŸ’¬ AnsweredOpened February 9, 2022by m-jojo-s1 reactions

Component.remove() in 'component:mount' does not remove the rendered view

Quick answerby artf❀ 1

Yeah, the problem here is the DOM node is created but not yet appended to the parent. You can defer the removal via setTimeout but that will still trigger the image activation. Probably I'll move that event once the node is appended.

Read full answer below ↓

Question

GrapesJS version

  • I confirm to use the latest version of GrapesJS

What browser are you using?

Chrome Version 98.0.4758.80 (Official Build) (arm64)

Reproducible demo link

https://jsfiddle.net/Lsjhxczp/10/

Describe the bug

How to reproduce the bug?

  1. Setup the component:mount hook to remove mounted component
  2. Add a new block/component

What is the expected behavior? The new component gets removed, both model and view.

What is the current behavior? Only the model is removed, view stays in place and isn't re-rendered after removal.

If is necessary to execute some code in order to reproduce the bug, paste it here below:

editor.on('component:mount', component => {
    if (component.is('image')) {
      component.remove();
    }
});

// the following has no effect
/* editor.on('component:create', component => {
    if (component.is('image')) {
      component.remove();
    }
}); */

Code of Conduct

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

Answers (2)

artfβ€’ February 11, 2022

Yeah, the problem here is the DOM node is created but not yet appended to the parent. You can defer the removal via setTimeout but that will still trigger the image activation. Probably I'll move that event once the node is appended.

ClaudeCodeβ€’ May 17, 2026

Thanks for reporting this, @m-jojo-s.

Great question about component.remove() in 'component:mount' does not remove the rendered view. The recommended approach with Components 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.