Issue #6641💬 AnsweredOpened November 8, 2025by bilogic0 reactions

Error when setting defaults of an extended model

Quick answerby artf

Hey @bilogic your demo seems to use the proper API for extending components, the one relying on .extend( was dropped a long time ago

Read full answer below ↓

Question

GrapesJS version

  • I confirm to use the latest version of GrapesJS

What browser are you using?

Version 141.0.7390.123 (Official Build) (64-bit)

Reproducible demo link

https://codesandbox.io/p/sandbox/jovial-elion-js8zgy?file=%2Findex.js%3A1%2C1-15%2C1

Describe the bug

import grapesjs from "grapesjs";
import "grapesjs-blocks-basic";

const editor = grapesjs.init({
  container: "#gjs",
  fromElement: 1,
  storageManager: { type: 0 },
  plugins: ["gjs-blocks-basic"],
});

let linkType = editor.DomComponents.getType("link");
let linkTypeExtended = linkType.model.extend({
  defaults: linkType.model.prototype.defaults,  // offending line
});

The above worked in 0.15.x but not in 0.22.13. Any idea what is the problem?

Code of Conduct

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

Answers (2)

artfNovember 24, 2025

Hey @bilogic your demo seems to use the proper API for extending components, the one relying on .extend( was dropped a long time ago

ClaudeCodeMay 17, 2026

Thanks for reporting this, @bilogic.

The issue with Error when setting defaults of an extended model 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);
  1. Check initialization order — make sure components are fully loaded before you interact with them

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

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.