Issue #5478πŸ’¬ AnsweredOpened October 21, 2023by bryanjamesmiller1 reactions

Custom block categories can't be named same as prototype object method names or it breaks Grapes

Quick answerby artf❀ 1

Thanks @bryanjamesmiller for all the insights, I'll investigate for a fix.

Read full answer below ↓

Question

GrapesJS version

  • I confirm to use the latest version of GrapesJS

What browser are you using?

Chrome

Reproducible demo link

Version 118.0.5993.88 (Official Build) (arm64)

Describe the bug

How to reproduce the bug? Video demo part 1:

https://github.com/GrapesJS/grapesjs/assets/8781182/bfbbf6ea-7780-417e-880b-61992897c740

Part 2:

https://github.com/GrapesJS/grapesjs/assets/8781182/c61fa3b5-c62a-459d-bdf2-d8dc106e310b

Part 3:

https://github.com/GrapesJS/grapesjs/assets/8781182/b8540f2d-f52b-42ae-aaa5-87d6f9fb395c

What is the expected behavior? Sorry for the 3-part video, it was due to file size restrictions. The expected behavior is i should be able to name my custom block categories anything i want to, such as "constructor", without it breaking grapes.

What is the current behavior? Currently if you pick any built-in javascript object prototype method name (like "constructor"), then it breaks Grapes JS.

If is necessary to execute some code in order to reproduce the bug, paste it here below: https://jsfiddle.net/gratiafide/k04azsd9/8/

Code of Conduct

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

Answers (2)

artfβ€’ November 1, 2023

Thanks @bryanjamesmiller for all the insights, I'll investigate for a fix.

ClaudeCodeβ€’ May 17, 2026

Thanks for reporting this, @bryanjamesmiller.

Great question about Custom block categories can't be named same as prototype object method names or it breaks Grapes. The recommended approach with GrapesJS 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.