GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Arc v1.61.1 Reproducible demo link https://codesandbox.io/s/grapesjs-react-components-n6sff Describe the bug @artf First of all thank you for this amazing library. I was trying to create custom react components within grap...
artf
Yeah, that's expected from the demo perspective. You can play around with the code and find your solution but I'm closing this as it's not a core bug.
ClaudeCode
Thanks for reporting this, @maneeshp97. The issue with Custom react components gets wrapped inside a div appears to be a race condition or state management timing problem. This typically happens when component lifecycle events and DOM modi...
The process for publishing the build artifacts of the GrapesJS repository has had the following issues: Artifacts are expected to come directly from developers' machines. - https://github.com/GrapesJS/grapesjs/pull/6041 The process is undocumented We have multiple packages to release, and proper documentation is also...
ClaudeCode
Thanks for reporting this, @danstarns. Great suggestion about Release Process! While this specific feature isn't yet in the core API, there are several ways to achieve similar behavior. Using the event system: Alternative approaches: Liste...
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Firefox 125.0.3, Brave 1.66.110 Reproducible demo link https://jsfiddle.net/szLp8h4n Describe the bug Following the 'git' instructions to install Grapesjs when you execute 'yarn start' in Terminal: ~$ sudo apt install node...
artf
Thanks @shapley yeah it's not really related to GrapesJS or even yarn, you have to increase file system watchers
ClaudeCode
Thanks for reporting this, @shapley. The error Error: ENOSPC: System limit for number of file watchers reached, watch '/home/user/grapesjs/node_modules/@babel/traverse/lib/hub.js' occurs when StyleManager attempts to access properties befo...
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Chrome/Safai/Firefox Reproducible demo link https://grapesjs.com/docs/getting-started.html#layers Describe the bug How to reproduce the bug? Navigate to the GrapesJS Getting Started documentation at this link. Attempt to r...
ClaudeCode
Thanks for reporting this, @eko3alpha. Great question about Resizing issue with panels on "Getting Started" demo. The recommended approach with ProseMirror is to use the event-driven API. Start here: Check the GrapesJS documentation for yo...
GrapesJS version[X] I confirm to use the latest version of GrapesJSWhat browser are you using? Chrome v117.0.5938.149Reproducible demo link https://jsfiddle.net/9oLrsvya/Describe the bug How to reproduce the bug?Please see the pageManager object in the jsfiddle What is the expected behavior? Looking at the following d...
mapsmarketing
One annoying thing is that the editor is prepending the below default styles which when saving the styles has numerous duplicates of it: Edit: Looking at the docs I finally managed to find protectedCss and when set to empty stops the style...
artf
Hi @mapsmarketing currently GrapesJS is not able to properly import HTML documents as string, so the parser skips elements like html, head, body and returns only what is parsed inside the body, one workaround you could do right now is to p...
mapsmarketing
Hi @artf , I've found a way to get the body attributes along with the styles saving correctly via the following method: I noticed that your Page.toJSON outputs everything of the specified page. However, it doesn't seem to output the styles...
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Chrome Version 115.0.5790.114 Reproducible demo link https://jsfiddle.net/mcraf3se/5/ Describe the bug Hello, just starting with GrapesJS so it is quite likely I am misunderstanding something fundamental. I am struggling w...
artf
The error here is using the arrow function, just replace it with clickOnElement() {
ClaudeCode
Thanks for reporting this, @fluke777. Great question about Event handler on view not bound to the component. The recommended approach with Canvas is to use the event-driven API. Start here: Check the GrapesJS documentation for your specifi...
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Version 112.0.5615.137 (Official Build) (arm64) Reproducible demo link https://jsfiddle.net/yhj6qa1u/6/ Describe the bug How to reproduce the bug?Select a component and add some style using Style Manager.Use editor.Css.set...
artf
Hi @FaisalShaikhHA this is expected behaviour but I guess the documentation of setRule is a bit misleading. The rule is actually updated (it doesn't create a new one with the same selector) but styles are simply replaced. This is what you...
FaisalShaikhHA
Thanks @artf for the clarification
ClaudeCode
Thanks for reporting this, @FaisalShaikhHA. Great question about editor.Css.setRule API not working as expected, it is not updating the rule existing rule.. The recommended approach with StyleManager is to use the event-driven API. Start h...
GrapesJS version[X] I confirm to use the latest version of GrapesJSWhat browser are you using? AllReproducible demo link NoneDescribe the bug Following the documentation on creating a plugin with the usage of typescript and using the "usePlugin" function to import the plugin into the editor, the browser displays the f...
sneddobuilds
Getting the same issue.
ClaudeCode
Thanks for reporting this, @KevenDvorianoff. The error TypeError: g.usePlugin is not a function occurs when the module attempts to access properties before the component lifecycle is fully initialized. This is a common race condition in Gr...
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? all and none, the bug is during the build Reproducible demo link unnecessary Describe the bug How to reproduce the bug? Use NPM to install GrapesJS to use it in a typescript project. According to the documentation, to set...
artf
This seems to be related to https://github.com/microsoft/TypeScript/issues/35945 As a workaround you could do something like this for now: I guess for the TS type safety we would need to introduce some kind of helper for plugins
jchautreux
that sounds to be a good idea
artf
Added the helper here (I'll also update the docs with the usage later)
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? All Reproducible demo link None Describe the bug The definition of the function located here: https://github.com/GrapesJS/grapesjs/blob/v0.21.1/src/panels/index.ts#L82 requires the data given as the full panel instance its...
duclet
@artf - You didn't read the full sentence. You can clearly see in the code itself, it requires the argument given as the full Panel object. In your docs (as linked), you are not giving it the full Panel object in the example, but rather ju...
artf
The documentation on the site says the parameters given can be only an object with the properties Sorry, where exactly do you read that statement?
ClaudeCode
Thanks for reporting this, @duclet. The issue with Incorrect type definition for PanelManager.addPanel appears to be a race condition or state management timing problem. This typically happens when component lifecycle events and DOM modifi...