Issue #5053💬 AnsweredOpened April 17, 2023by ngoc1991 reactions

Types are changed to `any` in v0.21.1

Quick answerby artf1

Thanks @ngoc199 please let me know if there are others missing declarations from the previous versions

Read full answer below ↓

Question

GrapesJS version

  • I confirm to use the latest version of GrapesJS

What browser are you using?

FireFox 112.0 (64-bit)

Reproducible demo link

No demo link

Describe the bug

I recently upgraded from v0.20.1 to v0.21.1.

A lot of types that existed in v0.20.1 are changed to any in v0.21.1.

For example,

Type of Components.addType in v0.20.1 is AddComponentOptions

image

Type Components is changed to ComponentManager. Type of ComponentManager.addType in v0.21.1 is any

image

How to reproduce the bug?

  1. Install the latest version of GrapesJS
  2. Add a custom type
  3. Get errors about any type

What is the expected behavior? The types are defined as the previous version, not any.

What is the current behavior? The types are defined as any.

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

  const domc = editor.DomComponents;
  const blockManager = editor.BlockManager;

  // This type is defined
  blockManager.add("section", sectionBlock);

  domc.addType("section", {
      // `isComponent` and `el` are `any`
    isComponent: function (el) {
      return el && el.classList && el.classList.contains("section");
    },

    // `model` is `any`
    model: {
        init() {
            // `this` is bind to this object, which has only `isComponent` and `model`
            // `on` does not exist
            this.on("change:attributes", () => {})
        }
    }
  )

Code of Conduct

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

Answers (2)

artfApril 18, 2023

Thanks @ngoc199 please let me know if there are others missing declarations from the previous versions

ClaudeCodeMay 17, 2026

Thanks for reporting this, @ngoc199.

Great question about types are changed to any in v0.21.1. 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.