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.
GJS Helper
The TypeError: g.usePlugin is not a function error in GrapesJS typically arises from a misunderstanding of how plugins are registered and loaded, specifically confusing the global grapesjs library object with an editor instance. Root Cause...
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 and none, the bug is during the build Reproducible demo link unnecessary Describe the bug How to reproduce the bug?create a blank projectuse NPM to install GrapesJS and a plugin (preset-webpage in this example but "wor...
artf
I'm closing this as related to https://github.com/GrapesJS/grapesjs/issues/5149
jchautreux
That's not really the same problem, in the #5149, the bug is related on how to set plugin options during the tool initialization. Here, the bug is related to the last update of the project that has defined a new index.d.ts that is not comp...
artf
In the previous release index.d.ts had the same signature for plugins so I'm not sure to what change you're referring to https://github.com/GrapesJS/grapesjs/blob/095466c8cc8034e54888d67beef4cb9296c823e4/index.d.ts#L50-L53 Can you share th...
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?
GJS Helper
Thank you for reporting this and bringing it to our attention. It's important to ensure clarity between type definitions and documentation. After reviewing the GrapesJS v0.21.1 source code and the documentation, it appears there isn't a di...
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Version 1.51.110 Chromium: 113.0.5672.77 (Offizieller Build) (64-Bit) Reproducible demo link https://grapesjs.com/docs/getting-started.html#add-blocks Describe the bug On Linux Wayland (Arch Linux and Gnome) using Brave yo...
artf
By checking with the same Brave version (on Mac), drag and drop seems to work properly, so it doesn't look like an issue with GrapesJS itself or the browser. If anybody else experience the same or have more context about the issue, please...
gxanshu
I'm facing the same issue with tauri. they use webgtk and drag & drop are not working there as well
putzwasser
By checking with the same Brave version (on Mac), drag and drop seems to work properly, so it doesn't look like an issue with GrapesJS itself or the browser. I don't feel this is a valid check. You got a completely different setup by using...
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? FireFox 112.0 (64-bit) Reproducible demo link No demo link Describe the bug I recently upgraded from v0.20.1 to v0.21.1. A lot of types that existed in v0.20.1 are changed to any in v0.21.1. For example, Type of Components...
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...
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Chrome 111 Reproducible demo link https://jsfiddle.net/zfkuq7sh/ Describe the bug Some texts are translated and some not. Some are translated only after I click some tool button, then its translated. For example Top bar bu...
artf
@applibs I can't help if you don't provide a valid reproducible demo, please include all the missing dependencies.
GJSBlock
Thanks for reporting this, @applibs. The issue with Localization works weird appears to be a race condition or state management timing problem. This typically happens when component lifecycle events and DOM modifications overlap, creating...
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? any Reproducible demo link no Describe the bug I believe many links of configuration objects in the docs are still to javascript files but the code has been updated to typescript <img width="1437" alt="Screenshot 2023-03-0...
GJSBlock
Thanks for reporting this, @himansh-gjr. The issue with broken links in the docs appears to be a race condition or state management timing problem. This typically happens when component lifecycle events and DOM modifications overlap, creat...
GrapesJS version[X] I confirm to use the latest version of GrapesJSWhat browser are you using? Chrome Version 110.0.5481.100 (Official Build) (arm64)Reproducible demo link NoneDescribe the bug I am trying to replicate in React the customizing the Block Manager like in this example Vue block manager, but the "block:cus...
artf
@besart-k you have to provide a reproducible demo as if it works with the current Vue demo example it shouldn't be different in React. Maybe you're using an old version of grapesjs or doing something wrong in your React app, so in this cas...
GJSBlock
Thanks for reporting this, @besart-k. Great question about block:custom is not working on React. The recommended approach with GrapesJS is to use the event-driven API. Start here: Check the GrapesJS documentation for your specific module L...
GrapesJS version[X] I confirm to use the latest version of GrapesJSWhat browser are you using? Chrome LatestReproducible demo link https://codesandbox.io/s/interesting-bell-xntbtrDescribe the bug How to reproduce the bug?go to the codesandboxdrag and drop Custom Code block.put this code inside the Custom Code editor a...
artf
This happens because of the button implementation in the forms plugin, which allows only textnodes as children. If you remove the form plugin you'll be able to see the <a> element (if you prefer you can also extend the button component wit...
handhikadj
so what is the code of "normal" implementation of the button? btw, may I know why do you make the button to behave like that on the forms plugin?
artf
If I recall properly the main reason there was a problem with inline text editing with button elements, so that approach was the easiest way to fix a common issue. I guess the "normal" implementation would be to skip/overwrite the init met...