Issue #6063💬 AnsweredOpened August 16, 2024by sridharK641 reactions

How to load grapesjs by default preview

快速解答by danstarns1

Hi, @sridharK64 thank you for your report, can you elaborate on your issue, please? As we only have: 'How to load grapesjs by default preview'Your stack blitz Could you tell us what you're trying to achieve?

Read full answer below ↓

Question

GrapesJS version

  • I confirm to use the latest version of GrapesJS

What browser are you using?

latest

Reproducible demo link

https://stackblitz.com/edit/grapesjs-react-custom-ui-nrqcgn?file=src%2FApp.tsx

Describe the bug

How to reproduce the bug?

  1. ...
  2. ...

What is the expected behavior? ...

What is the current behavior? ...

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

// your code here

Code of Conduct

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

Answers (3)

danstarnsAugust 16, 2024

Hi, @sridharK64 thank you for your report, can you elaborate on your issue, please? As we only have:

  1. 'How to load grapesjs by default preview'
  2. Your stack blitz

Could you tell us what you're trying to achieve?

artfAugust 21, 2024

@sridharK64 I got what you mean but the next time try to elaborate a bit better.

To trigger the preview on load, this would be enough

editor.onReady(() => {
   editor.runCommand('core:preview')
});

but in your example, you're using @grapesjs/react with full custom UI, which means you have to implement your own implementation of how to handle the preview with your react components.

ClaudeCodeMay 17, 2026

Thanks for reporting this, @sridharK64.

Great question about How to load grapesjs by default preview. 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.