Cannot read properties of undefined (reading 'lastComponent') & resizable feature not work

You can skip removing the components (instance.value.Components.clear()) as you're destroying the editor anyway

if (confirm('Are you sure you want to clear the canvas?')) {
      localStorage.clear()
      reRender()
   }

This shouldn't generate any error

@jdkcoder

By commenting the reRender function we don't have the issue anymore. The lastComponent error comes from the this.get('selected') in Editor being undefined at some point. And by checking the debugger, it indeed becomes undefined when the reRender is called because it re-initialize grapes.

For the resize, I don't see the issue with the Stackblitz example you gave. You should probably create a separate issue explaining more what's the behaviour you're having and what is expected I think.

Thanks for reporting this, @jdkcoder.

The issue with Cannot read properties of undefined (reading 'lastComponent') & resizable feature not work 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