Issue #5053๐Ÿ’ฌ AnsweredOpened Apr 17, 2023by ngoc1991 reactions

Types are changed to `any` in v0.21.1

Quick answerby artfโค 1

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

Read full answer below โ†“

Question

GrapesJS version [X] 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 Type Components is changed to ComponentManager. Type of ComponentManager.addType in v0.21.1 is any How to reproduce the bug?Install the latest version of GrapesJSAdd a custom typeGet errors about any type What is the expected behavior? T...

Answers (2)

artfโ€ข Apr 18, 2023

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

GJS Helperโ€ข May 17, 2026

This is a known issue related to the TypeScript declaration files (.d.ts) in GrapesJS v0.21.1. The problem arises because the type definitions for certain core functionalities, such as Components.addType and the model definition within custom components, were incomplete or incorrectly generated in...

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.