Issue #5330πŸ’¬ AnsweredOpened August 24, 2023by rozek0 reactions

Latest version (commit 4f0c5b1) no longer compiles without errors

Quick answerby artf

Thanks @rozek I'll fix it now

Read full answer below ↓

Question

GrapesJS version

  • I confirm to use the latest version of GrapesJS

What browser are you using?

none

Reproducible demo link

none

Describe the bug

yarn build fails with two errors:

ERROR in /Users/andreas/rozek/GitHub/grapesjs/test/specs/utils/Sorter.ts
438:19-35
[tsl] ERROR in /Users/andreas/rozek/GitHub/grapesjs/test/specs/utils/Sorter.ts(438,20)
      TS2532: Object is possibly 'undefined'.
ts-loader-default_4a384f05a8be7d44

ERROR in /Users/andreas/rozek/GitHub/grapesjs/test/specs/utils/Sorter.ts
489:19-35
[tsl] ERROR in /Users/andreas/rozek/GitHub/grapesjs/test/specs/utils/Sorter.ts(489,20)
      TS2532: Object is possibly 'undefined'.
ts-loader-default_4a384f05a8be7d44

This may just be a problem with TypeScript being too picky, because

  1. you may disable the error messages using // @ts-ignore and compile again
  2. the tests will run fine then.

but since I'm new to GrapesJS, I can not judge myself. Anyway, it's normally not a good idea to just // @ts-ignore TypeScript errors...

Code of Conduct

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

Answers (3)

artfβ€’ August 25, 2023

Thanks @rozek I'll fix it now

rozekβ€’ August 25, 2023

thank you very much!

ClaudeCodeβ€’ May 17, 2026

Thanks for reporting this, @rozek.

The issue with latest version (commit 4f0c5b1) no longer compiles without errors appears to be a race condition or state management timing problem. This typically happens when component lifecycle events and DOM modifications overlap, creating an inconsistent state.

What to try:

  1. Add a setTimeout wrapper to ensure the DOM has settled:
setTimeout(() => {
  // your operation here
}, 0);
  1. Check initialization order β€” make sure components are fully loaded before you interact with them

  2. Use the editor's event system β€” listen to completion events:

editor.on('component:mount', (component) => {
  // safe to interact with component here
});

Recommended next steps:

  • Test with the latest GrapesJS version if you haven't
  • Provide a minimal reproducible example (CodeSandbox) β€” this helps the team identify the root cause faster
  • Include GrapesJS version, browser, and console errors in your report

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.