Issue #5148💬 AnsweredOpened May 29, 2023by jchautreux0 reactions

None of the official GrapesJS plugins works with the new index.d.ts

Quick answerby artf

I'm closing this as related to https://github.com/GrapesJS/grapesjs/issues/5149

Read full answer below ↓

Question

GrapesJS version

  • I confirm to use the latest version of GrapesJS

What browser are you using?

all and none, the bug is during the build

Reproducible demo link

unnecessary

Describe the bug

How to reproduce the bug?

  1. create a blank project
  2. use NPM to install GrapesJS and a plugin (preset-webpage in this example but "works" for all official plugins)
  3. load GrapesJS using import GrapeJS from 'grapesjs'
  4. attempt to load preset-webpage using import plugin from 'grapesjs-preset-webpage';

What is the expected behavior? the project build correctly and the plugin is available

What is the current behavior? the project failed to build because the d.ts of GrapeJS has changed

FYI I could have created this ticket in each official plugins but I think one ticket to remind to update all is enough

Code of Conduct

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

Answers (4)

jchautreuxMay 30, 2023

That's not really the same problem, in the #5149, the bug is related on how to set plugin options during the tool initialization. Here, the bug is related to the last update of the project that has defined a new index.d.ts that is not compatible with the way of the plugins used it previously

ClaudeCodeMay 17, 2026

Thanks for reporting this, @jchautreux.

Great question about none of the official GrapesJS plugins works with the new index.d.ts. The recommended approach with GrapesJS 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.