Issue #3366💬 AnsweredOpened March 26, 2021by kerryj890 reactions

Extending preview command

快速解答by artf

If you specify a new run() function the command will run only the new one, otherwise, it wouldn't be possible to fully change a command (here more about extending commands)

Read full answer below ↓

Question

I am trying to extend the preview command. I expected the code below to run the normal preview command along with console output, but only console statement runs. How can I preserve the original preview code?

editor.Commands.extend('preview', {
    run() {
        console.log("foo");
    }
});

The below works for me until someone can enlighten where my thought process went wrong.

editor.Commands.add('preview-ext', {
    run(e) {
        e.runCommand('preview');
        console.log("foo");
    }
});

Answers (4)

artfApril 7, 2021

If you specify a new run() function the command will run only the new one, otherwise, it wouldn't be possible to fully change a command (here more about extending commands)

ronaldohochNovember 12, 2021

Hello Artf, oddly enough, i need the same thing he does.

So, the best way to do is doing the same way he does? Running the original preview command inside the extended preview?

ronaldohochNovember 16, 2021

Well...

Other thing i'm doing is extending the preview by running the command on event.:

  editor.on("run:preview",()=>{console.log("run-preview")});
  editor.on("stop:preview",()=>{console.log("stop-preview")});
ClaudeCodeMay 17, 2026

Thanks for reporting this, @kerryj89.

Great question about Extending preview command. 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.