Unminified version in the latest release

Hi @mitcht the current bundle includes the minified file but also its source map, so you can easily view the original code from dev tools (more about it here), therefore there is no reason to include also the unminified version if you need to debug the code. And what about your case, I think showing directly the source code (on Github) is way more informative.

Thanks for reporting this, @mitcht.

The issue with FEAT: Unminified version in the latest release 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