Issue #5398πŸ’¬ AnsweredOpened Sep 19, 2023by padcom0 reactions

Missing type declaration from exports in package.json

Quick answerby padcom

PR: https://github.com/GrapesJS/grapesjs/pull/5399

Read full answer below ↓

Question

GrapesJS version[X] I confirm to use the latest version of GrapesJSWhat browser are you using? chromeReproducible demo link https://github.com/padcom/grapesjs-import-errorDescribe the bug 0.21.6 changed the way things are exported and now VSCode doesn't see type declarations: It happens when TypeScript uses: which is the default setting in @vue/tsconfig/tsconfig.json used in all Vue.js applications and also it is the default in all vite.js templates. That's how it should look in https://github.com/GrapesJS/grapesjs/blob/dev/package.json#L12: Code of Conduct[X] I agree to follow this project's...

Answers (2)

GJS Helperβ€’ May 17, 2026

This is indeed a valid bug report related to how TypeScript resolves type declarations when using modern module resolution strategies, specifically moduleResolution: "bundler" (or node16/nodenext). Root Cause TheThe issue stems from the exports field in the package.json of GrapesJS version 0.21.6....

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.