Two command names (new and old) cause the command division.
No community answers yet. Open the original discussion on GitHub to share your solution.
Question
For some predefined commands, has a new name and old name. It tells the user to use the new one as preferred. If choosing the new command name to extend, will not works, that because of old names in the internal. The reason is: In commands/index.js, the added or extended commands are the newly created views (extends from CommandAbstract). Here is my code snippet, it not works if the defaultCommand option value is select-comp
Answers (0)
No answers yet.
Related Questions and Answers
Continue research with similar issue discussions.
Issue #5263
Deleting a component without deleting its corresponding style, will adding new components later cause style conflicts?
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? latest version of Chrome Reproducible demo...
Issue #3265
RenderField in traitView does not handle null or undefined
Hi @artf! Working on the editor on one of my custom traits i had an issue where for some reason that is not important, the createInput was...
Issue #5148
None of the official GrapesJS plugins works with the new index.d.ts
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? all and none, the bug is during the build...
Issue #3307
Provide a not minified version
Is there a single file version of grapesjs that is not minified? It would be nice to have one for bug fixing and quick testing of new featu...
Paid Plugins That Match This Issue
Curated by issue keywords and label relevance to help you ship faster.
Loading paid plugin recommendations...
Check the open-source GrapesJS plugins on GitHub or run a quick search in our free catalog.
Browse free plugins β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.
Tutorial
Vanilla GrapesJS vs GrapesJS With Plugins: What You Actually Get Out of the Box (2026)
New to GrapesJS? See exactly what the stock editor gives you, where it falls short, and which plugins close the gaps β a beginner-friendly 2026 comparison
Tutorial
GrapesJS DevTools: A Developer Panel Inside Your Editor
If you've ever debugged GrapesJS with console.log(editor.getSelected()) and a dozen throwaway event listeners β this post is for you.
Tutorial
How We Built Composeit in Record Time Using GrapesJS Shadcn
Bypass foundational builder boilerplate and focus on what truly matters.
Browse Plugin Categories
Jump directly to plugin category pages on the marketplace.