GrapesJS version [x] I confirm to use the latest version of GrapesJS What browser are you using? Chrom v140.0.7307.0 (canary) Reproducible demo link https://jsfiddle.net/y3gr69s4/ Describe the bug How to reproduce the bug? Create editor instance with parser.optionsHtml.keepEmptyTextNodes option set true. Load HTML cod...
ClaudeCode
Thanks for reporting this, @nanto. Great question about parser ignores parser.optionsHtml.keepEmptyTextNodes option. The recommended approach with StyleManager is to use the event-driven API. Start here: Check the GrapesJS documentation fo...
The codebase currently uses outdated versions of TypeScript. This ticket aims to: Upgrade to the latest version of TypeScript. Ensure consistent TypeScript configurations across all projects. Integrate TypeScript into the development and CI pipelines for automated type checking. Updating and standardizing TypeScript w...
ClaudeCode
Thanks for reporting this, @danstarns. The issue with Typescript appears to be a race condition or state management timing problem. This typically happens when component lifecycle events and DOM modifications overlap, creating an inconsist...
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? chrome Reproducible demo link i have given the code in issues Describe the bug Screencast from 12-06-24 03:09:58 PM IST.webm problem is right after applying any bold or italic it is getting disappeard once i click somewher...
artf
From the official demo it looks to work as expected, so I guess it's related to your custom logic. Please provide a minimal reproducible demo of the issue.
ClaudeCode
Thanks for reporting this, @adarshsingh197. The error error: any) { occurs when ProseMirror attempts to access properties before the component lifecycle is fully initialized. This is a common race condition in GrapesJS. Immediate workaroun...
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Chrome v122 Reproducible demo link not applicable Describe the bug The GrapeJs Docs indicate that it is possible to add mixed content to the "content" property of a block (see https://grapesjs.com/docs/modules/Blocks.html#...
ClaudeCode
Thanks for reporting this, @rhoenerSBS. Great question about Wrong Type for "content" property in BlockProperties. The recommended approach with Components 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 GrapesJS What browser are you using? Chrome v122 Reproducible demo link not applicable Describe the bug The ColorPicker Interface that came with the latest release, defines the "preferredFormat" option to expect a 'boolean' value but the docs of the Spectrum...
ClaudeCode
Thanks for reporting this, @rhoenerSBS. Great question about Wrong Type in ColorPickerOptions Interface. The recommended approach with GrapesJS is to use the event-driven API. Start here: Check the GrapesJS documentation for your specific...
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Firefox Version 123.0 (64-bit) Reproducible demo link Not present Describe the bug I guess most of the .js files have been turned into typescript but there might be more broken links like the below one.. Code of Conduct [X...
ClaudeCode
Thanks for reporting this, @afrinxnahar. The issue with broken link in the API docs appears to be a race condition or state management timing problem. This typically happens when component lifecycle events and DOM modifications overlap, cr...
GrapesJS version[X] I confirm to use the latest version of GrapesJSWhat browser are you using? chromeReproducible demo link https://github.com/padcom/grapesjs-import-errorDescribe the bug 0.21.6 changed the way things are exported and now VSCode doesn't see type declarations: It happens when TypeScript uses: which is...
Thanks for reporting this, @padcom. The issue with Missing type declaration from exports in package.json appears to be a race condition or state management timing problem. This typically happens when component lifecycle events and DOM modi...
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Chrome Reproducible demo link https://jsfiddle.net/vmeywbk8/11/ Describe the bug Just a small type issue we came across - when adding an action to the RichTextEditor, the "icon" property of RichTextEditorAction is marked a...
ClaudeCode
Thanks for reporting this, @peters-ben-0007. The issue with (type issue) cannot pass HTMLElement as icon when adding new rte action appears to be a race condition or state management timing problem. This typically happens when component li...
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? none Reproducible demo link none Describe the bug yarn build fails with two errors: This may just be a problem with TypeScript being too picky, becauseyou may disable the error messages using // @ts-ignore and compile agai...
artf
Thanks @rozek I'll fix it now
rozek
thank you very much!
ClaudeCode
Thanks for reporting this, @rozek. The issue with latest version (commit 4f0c5b1) no longer compiles without errors appears to be a race condition or state management timing problem. This typically happens when component lifecycle events a...
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...