Customize your GrapesJS

Oh I know that! What I was referring to is that if you try and use the index/block/component files from dist (ie unminified and easier to work from) they don't work outside of a node/webpack environment.

On 19 Aug 2019, at 20:18, Pouya Miralayi [email protected] wrote:

@smik3 you do not need node environment for defining plugins. grapesjs.plugins.add('your-plugin', editor => { your stuff } this will define the behavior and you have the editor instance available to you as argument. then initialize your editor as before and specify the plugin. cheers.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

@smik3 , this is not a good practice, as it won't let you update GrapesJS easy in future. You better separate the custom code in js functions and whichever of them you need to use as a plugin, you can load. Or use node only for compilation of your plugin and put the plugin-name.min.js in production.

var editor = grapesjs.init({ ... plugins: [yourCustomFunction], ... })

Hey, @GoodPHP I need help with a challenge I've been facing

I want to hide images with src empty on preview mode and show them on editor mode i.e stop: preview.

I've tried this but it doesn't seem to work for some reason

editor.on('run:preview', () => {
    $('.img[src=""]').hide();
});

Thanks, Chaitu