Issue #6671Opened December 9, 2025by padcom1 reactions

BUG: `component.closestType()` is undefined

Question

GrapesJS version

  • I confirm to use the latest version of GrapesJS

What browser are you using?

any

Reproducible demo link

https://github.com/padcom/grapesjs-closestType-missing

Describe the bug

This bug was introduced in here. Before this change everything was working as expected. I presume the reset event is responsible for it.

What's even more annoying with it is that if you reload the page then the only console.log you'll see is with the undefined component.closestType() which means that if the component:update:components event is being used in conjunction with component.closestType() then the project is empty and broken.

How to reproduce the bug?

  1. clone https://github.com/padcom/grapesjs-closestType-missing
  2. npm install && npm start
  3. navigate to http://localhost:5173
  4. put Column component on the canvas
  5. put Text component inside the Column from pt 4
  6. observe console

What is the expected behavior? One should see the implementation of component.closestType in all logs

What is the current behavior? The first time this event is emitted the component.closestType is undefined

Code of Conduct

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

Answers (1)

padcomDecember 10, 20251 reactions

It turns out the second parameter is not always the component but the sender of the event which means that sometimes it is the collection of components which obviously doesn't have the closestType() method.

Thanks @artf for explaining it to me!

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...

Browse Plugin Categories

Jump directly to plugin category pages on the marketplace.