Feature Request: React 19 Compatibility

[tamofplease]

Description

First, thank you for the fantastic work on the @grapesjs and @grapesjs/react package! It has been incredibly useful for integrating GrapesJS into React projects.

However, I encountered a runtime error when using @grapesjs/react in a project that utilizes React 19. This seems to be caused by version incompatibility between React 18 (used during the build of @grapesjs/react) and React 19 (used in my project).

Problem Details

When I attempt to use @grapesjs/react in a React 19 project, the application throws runtime errors related to React's internal state handling, likely due to multiple React versions being resolved. For example:

• Errors related to ReactCurrentDispatcher
• Hooks or state-related APIs behaving unexpectedly

This issue appears to stem from the fact that @grapesjs/react is built with React 18, while my project uses React 19.

Reproduction

If helpful, I can create a minimal branch or repository to demonstrate the issue. Please let me know if this would be beneficial.

---

Request

Are there any plans to officially support React 19 in @grapesjs/react? Supporting both React 18 and React 19 would be ideal for broader compatibility.

In our current project, we rely heavily on GrapesJS and are planning to migrate to React 19. However, due to this runtime error, we are unable to proceed with the migration.

If official support for React 19 is planned, that would be greatly appreciated. However, if not (or if this is not feasible in the near future), we would consider forking the project and making the necessary changes on our side.