GrapesJS Issues

yashvi2026

how to use enable editing editor.getSelected().view.enableEditing(); this gives an error

GJS Helper

The issue "editor is undefined" when trying to use enableEditing in the browser console indicates that the GrapesJS editor instance is not accessible in the current scope of your console. The enableEditing method is part of the GrapesJS ed...

artf

Please avoid creating bug issues if you don't have any reproducible link

GJS Helper

The "namespace not found" error when installing GrapesJS plugins like grapesjs-basic-blocks or tui-image-editor in an Angular application typically indicates an issue with how the modules are being imported and initialized, or how their de...

artf

Thanks @Baghunts, good catch. Current workaround would be .addStyle({ 'border-left': '...' })

GJS Helper

The issue where a background-image style isn't applied correctly to a component in GrapesJS is typically due to one of two common reasons: incorrect CSS url() syntax or the component lacking sufficient dimensions to display the background....

artf

As explained here you should not reimport the output HTML to edit the project, only the JSON.

GJS Helper

The issue you've encountered where a component's script function runs twice after saving and reloading the page is a known behavior (or a bug, depending on the perspective) in GrapesJS's script management system. It stems from how GrapesJS...

davidrhoderick

Funnily enough, the CSS-based styling works.

artf

Looks like the Parcel transformer is trying to import codemirror/lib/codemirror.js instead of codemirror/lib/codemirror.css on this line: So I'd suggest to open the issue on the related package

GJS Helper

The issue you're encountering, @parcel/transformer-sass: expected "{" when importing GrapesJS SCSS, is a common problem related to how module bundlers like Parcel resolve and process stylesheet imports, especially when dealing with third-p...

artf

The behaviour is correct as style:property:update triggers on any update of the Style Manager Property (not only its value). So for your specific case you would need to update the callback in this way

SagarMaria

Hi @artf, thanks for the quick reply, but actually, part of the problem is still that even after making a change e.g. click "center" align radio option with the if statement you suggested, subsequent selections of that component still log...

GJS Helper

The issue you're encountering with style:property:update and Property onChange firing excessively, even on component selection, is a common point of confusion. The style:property:update event is a low-level event that triggers whenever a s...

DanavsSite

DanavsSite

i just found out its because of webview2.Support for webview2??!

artf

I think this is more related to some Tauri configuration instead of GrapesJS as we're using the native HTML5 drag and drop

artf

This is similar to this one, you have to put the editor instance outside of the Vue instance in order to bypass its proxies

GJSBlock

Thanks for reporting this, @TO-JHummel. Great question about Crash when dragging into nested components with Vue+Vite.. The recommended approach with GrapesJS is to use the event-driven API. Start here: Check the GrapesJS documentation for...

artf

@Spiral1234 if you're not able to reproduce the issue it's probably something on your end and without a reproducible demo it's hard to understand what might be a problem

GJS Helper

The issue you're encountering stems from how GrapesJS processes and normalizes styles, particularly inline styles, when importing HTML. Let's break down the root cause and provide the correct approach. Root Cause Explanation When GrapesJS...

artf

Thanks @ngoc199 please let me know if there are others missing declarations from the previous versions

GJS Helper

This is a known issue related to the TypeScript declaration files (.d.ts) in GrapesJS v0.21.1. The problem arises because the type definitions for certain core functionalities, such as Components.addType and the model definition within cus...