Issue #4801πŸ’¬ AnsweredOpened December 23, 2022by eduardocalixtokorp1 reactions

React components componentWillUnmount is not called

Quick answerby eduardocalixtokorp❀ 1

I've noticed that in my component definition I was doing reactRoot.render(<>{reactEl} </>) in onRender() then, I was missing to add root.unmount() n remove() method

Read full answer below ↓

Question

GrapesJS version

  • I confirm to use the latest version of GrapesJS

What browser are you using?

Chrome 108.0.5359.125 (Windows)

Reproducible demo link

https://codesandbox.io/s/white-meadow-o56l2d?file=/src/Chart/Chart.js:135-254 This demo is not in the latest grapesjs version, but locally, using the latest version, I have the same bug

Describe the bug

How to reproduce the bug?

  1. Go to this link
  2. Open the Console
  3. Drag a "Chart" Block to Body
  4. Check that "chart created" is logged
  5. Delete the chart
  6. "chart removed" isn't logged.

What is the expected behavior? ReactComponent.componentWillUnmount() / componentWillUnmount for functional components should be called when a component is deleted

What is the current behavior? ReactComponent.componentWillUnmount is not called, but mount is.

Code of Conduct

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

Answers (2)

eduardocalixtokorpβ€’ December 27, 2022

I've noticed that in my component definition I was doing reactRoot.render(<>{reactEl} </>) in onRender() then, I was missing to add root.unmount() n remove() method

ClaudeCodeβ€’ May 17, 2026

Thanks for reporting this, @eduardocalixtokorp.

Great question about React components componentWillUnmount is not called. 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.