Issue #4940πŸ’¬ AnsweredOpened February 21, 2023by mani-rai0 reactions

Destroying and re-initializing produces "Cannot read properties of undefined (reading 'get')"

Quick answerby artf

Yeah, the editor instance is not expected to be destroyed immediately due to some deferred async functions (eg. for the StorageManager) but that can be fixed. For now you can overcome the issue by doing something like this:

Read full answer below ↓

Question

GrapesJS version

  • I confirm to use the latest version of GrapesJS

What browser are you using?

Google Chrome Version 110.0.5481.100 (Official Build) (64-bit)

Reproducible demo link

https://stackblitz.com/edit/js-3urscf?file=index.html,index.js

Describe the bug

How to reproduce the bug?

  1. Initialize the editor
  2. Destroy the editor
  3. Initialize the editor again

What is the expected behavior? The code used is just a starter code from the official doc. It should be re-initialized without any problem.

What is the current behavior? Multiple errors are show in console.

TypeError: Cannot read properties of undefined (reading 'get') at o.runDefault (Editor.ts:874:28) at n.updateOffset (FrameWrapView.ts:89:8) at _e (_executeBound.js:8:65) at n.eval (bind.js:10:12) at n.eval (restArguments.js:16:27) at l (debounce.js:17:37)

Another:

Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'forEach') at s (Editor.ts:317:20) at o.eval (Editor.ts:336:9) at eval (grapes.min.js:2:911116) at Object.eval [as next] (grapes.min.js:2:911221) at eval (grapes.min.js:2:910096) at new Promise (<anonymous>) at nh (grapes.min.js:2:909838) at eval (Editor.ts:326:18)

If is necessary to execute some code in order to reproduce the bug, paste it here below:

// Not Necessary

Code of Conduct

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

Answers (2)

artfβ€’ February 23, 2023

Yeah, the editor instance is not expected to be destroyed immediately due to some deferred async functions (eg. for the StorageManager) but that can be fixed. For now you can overcome the issue by doing something like this:

setTimeout(() => {
  editor.destroy();
  ...
ClaudeCodeβ€’ May 17, 2026

Thanks for reporting this, @mani-rai.

Great question about Destroying and re-initializing produces "Cannot read properties of undefined (reading 'get')". The recommended approach with ProseMirror is to use the event-driven API.

Start here:

  1. Check the GrapesJS documentation for your specific module
  2. Look for the on() event listener method
  3. Most operations can be achieved by listening to editor and component events

Common patterns:

// Listen for changes
editor.on('change', () => console.log('something changed'));

// Component lifecycle
editor.on('component:mount', (c) => console.log('component ready', c));
editor.on('component:update', (c) => console.log('component updated', c));

If you're still stuck:

  • Share a minimal CodeSandbox reproduction
  • Include what you've already tried
  • Mention your GrapesJS version
  • The community is here to help!

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.