Setting the text content programmatically clears it in the canvas

Try using the .getEl method on the component then setting the element directly.

const editor = grapesjs.init({
  container: '#gjs',
  fromElement: 1,
  height: '100%',
  storageManager: { type: 0 },
  plugins: ['gjs-blocks-basic']
});

setTimeout(() => {
  const component = editor.getWrapper().find('.test-text')[0]
  const el = component.getEl();
  el.textContent = "test"
}, 1000)

  const component = editor.getWrapper().find('.test-text')[0]
  const el = component.getEl();
  el.textContent = "test"

Problem with this is that when you export the HTML, it returns the old text.

setTimeout(() => {
  const component = editor.getWrapper().find('.test-text')[0]
  const el = component.getEl();
  el.textContent = "test"

  console.log(component.toHTML())
  // <div class="test-text" id="i387">Hello World!!!</div>
}, 1000)

@mannyyang where did you find the usage of set('content', ...? It's more like private property and you should never use it.

To update inner components programmatically use component.components('test')

Thanks for reporting this, @mannyyang.

Great question about Setting the text content programmatically clears it in the canvas. 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!