Issue #5775πŸ’¬ AnsweredOpened March 26, 2024by ctrhub0 reactions

Component.get('traits').clone() is no longer available.

Quick answerby artf

If you need to make a copy of traits I'd suggest simply doing this JSON.parse(JSON.stringify(editor.getSelected().getTraits())). I don't remember ever mentioning cloning traits in docs, so I'd avoid using non-public APIs.

Read full answer below ↓

Question

GrapesJS version

  • I confirm to use the latest version of GrapesJS

What browser are you using?

Arc Version 1.35.0 / Chromium Engine 123.0

Reproducible demo link

https://grapesjs.com/demo.html

Describe the bug

How to reproduce the bug?

  1. Open dev tools
  2. Select a component
  3. Run in console:
const selectedComponent = editor.getSelected();
selectedComponent.get('traits').clone();

What is the expected behavior? Should return cloned version.

What is the current behavior? Throws an error:

Traits.ts:29 Uncaught TypeError: Cannot read properties of undefined (reading 'Traits')

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

const selectedComponent = editor.getSelected();
selectedComponent.get('traits').clone();

Note: .clone() is the only method I found that no longer works. Link to the method - https://arc.net/l/quote/ztapwusb

Code of Conduct

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

Answers (2)

artfβ€’ April 1, 2024

If you need to make a copy of traits I'd suggest simply doing this JSON.parse(JSON.stringify(editor.getSelected().getTraits())). I don't remember ever mentioning cloning traits in docs, so I'd avoid using non-public APIs.

ClaudeCodeβ€’ May 17, 2026

Thanks for reporting this, @ctrhub.

Great question about component.get('traits').clone() is no longer available.. The recommended approach with Components 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.