Wrapper styling

Yes @kuhelbeher, now the wrapper is created post plugins, so you can entirely extend it as any other component

LE: I have found a way. I am overwritting the stylable array from getWrapper() but I'm not 100% sure this is the correct way. Can you confirm this?

Yeah sure it's ok, but if you need, you can change the wrapper properties on init via mainConfig.domComponents.wrapper option https://github.com/artf/grapesjs/blob/18b2f95b7f844578dc2b28d786b126013d155d9e/src/dom_components/config/config.js#L9

you can change the wrapper properties on init via mainConfig.domComponents.wrapper option https://github.com/artf/grapesjs/blob/18b2f95b7f844578dc2b28d786b126013d155d9e/src/dom_components/config/config.js#L9

Hello, I've noticed that this options is for old version of grapesjs, but in new version wrapper property is removed from domComponents config. Is there a way to set some wrapper properties on initialization in new version?

Thanks for reporting this, @RaresVlaiduc.

Great question about Wrapper styling. The recommended approach with Components 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!