Issue #4240💬 AnsweredOpened April 5, 2022by varadero1 reactions

"index.d.ts is not a module" in 0.18.4 when grapesjs is imported with "import * as grapesjs from 'grapesjs';"

Quick answerby artf1

Should be fixed here https://github.com/artf/grapesjs/pull/4216 I guess you should disable TS for the current version.

Read full answer below ↓

Question

GrapesJS version

  • I confirm to use the latest version of GrapesJS

What browser are you using?

Chrome 99

Reproducible demo link

No link

Describe the bug

How to reproduce the bug?

  1. I was using grapesjs 0.18.2 in my typescript angular class imported like this - import * as grapesjs from 'grapesjs';
  2. Upgraded to 0.18.4

What is the expected behavior? No errors

What is the current behavior? Typescript complains at the line import * as grapesjs from 'grapesjs'; with the following error:

node_modules/grapesjs/index.d.ts' is not a module.ts(2306)

The 'grapesjs' part of the import has red squiggles. I suppose this is because index.d.ts was introduced in 0.18.4 (https://github.com/artf/grapesjs/releases/tag/v0.18.4)

image

Version 0.18.3 does not have this problem.

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

import * as grapesjs from 'grapesjs';

Code of Conduct

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

Answers (3)

aharishsundharJune 3, 2022

@artf im using grapesjs latest version ^0.18.4 i install npm grapesjs to run it its error on index.d.ts file can you please update issue npm install: Screenshot from 2022-06-03 12-12-01 manually change it local:

Screenshot from 2022-06-03 12-15-15 manully update it my side can you please update the modules side I REPLACE TYPE ANY Screenshot from 2022-06-03 12-15-28

ClaudeCodeMay 17, 2026

Thanks for reporting this, @varadero.

Great question about "index.d.ts is not a module" in 0.18.4 when grapesjs is imported with "import * as grapesjs from 'grapesjs';". The recommended approach with ProseMirror 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.