Editor takes a long time to load (sometimes over 1 minute)

Thanks @MisterKeyboard for providing the JSON.

Your project contains 10K style rules, which is a lot, but still, I'd not expect the load to be impacted that much. @mohamedsalem401 I think we need to verify if data source related changes (eg. StyleableModel.set) are not impacting too much there 🤔

@artf Will take a look and give an update on this.

@MisterKeyboard can you share the JSON of the project so we can verify that

Thanks for reporting this, @MisterKeyboard.

The issue with Editor takes a long time to load (sometimes over 1 minute) 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