Issue #5305💬 AnsweredOpened August 13, 2023by rajevar0 reactions

"component:add" event triggers when components are moved

Quick answerby artf

Hi @rajevar I think you're looking for component:create event, as component:add works as expected (eg. might be used to track any new movement inside a specific component)

Read full answer below ↓

Question

GrapesJS version

0.21.4

  • I confirm to use the latest version of GrapesJS

What browser are you using?

Chrome Version 113.0.5672.63

Reproducible demo link

https://jsfiddle.net/szLp8h4n/11/

Describe the bug

How to reproduce the bug? Move any of the text components around in the page. An alert will be displayed.

could be a regression. https://github.com/GrapesJS/grapesjs/issues/868 Don't see an option to reopen the bug, so creating new one.

What is the expected behavior? Alert will be displayed only on adding a new components to the canvas

What is the current behavior?

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

// your code here

Code of Conduct

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

Answers (2)

artfAugust 15, 2023

Hi @rajevar I think you're looking for component:create event, as component:add works as expected (eg. might be used to track any new movement inside a specific component)

ClaudeCodeMay 17, 2026

Thanks for reporting this, @rajevar.

Great question about "component:add" event triggers when components are moved. The recommended approach with Canvas 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.