Error: node_modules/grapesjs/dist/index.d.ts:12551:2 - error TS1005: '?' expected. 12551 }> ? C : {}) | undefined) => (editor: Editor) => void; ~ Error: node_modules/grapesjs/dist/index.d.ts:12558:3 - error TS1005: '?' expected. 12558 }> ? C : {}) | undefined) => (editor: Editor) => void;

@artf can you please check this one

I use safari and chrome

On Tue, Sep 12, 2023 at 10:52 PM Akshay jangid @.***> wrote:

@artf https://github.com/artf can you please check this one

— Reply to this email directly, view it on GitHub https://github.com/GrapesJS/grapesjs/issues/5377#issuecomment-1716989704, or unsubscribe https://github.com/notifications/unsubscribe-auth/ANQ6NOR2BYRPPRYFJF5ZGLDX2FC3TANCNFSM6AAAAAA4TBTVBU . You are receiving this because you are subscribed to this thread.Message ID: @.***>

+1 after upgrade

Thanks for reporting this, @Akkiiiiiii.

The issue with Error: node_modules/grapesjs/dist/index.d.ts:12551:2 - error TS1005: '?' expected. 12551 }> ? C : {}) | undefined) => (editor: Editor) => void; ~ Error: node_modules/grapesjs/dist/index.d.ts:12558:3 - error TS1005: '?' expected. 12558 }> ? C : {}) | undefined) => (editor: Editor) => void; 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);

2. Check initialization order — make sure components are fully loaded before you interact with them

3. 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