What browser are you using?
Firefox
Describe the bug
How to reproduce the bug?
Set up a React 19 project with @grapesjs/studio-sdk@1.1.1
Render the GrapesJsStudio component
Open the browser console or check the Next.js error overlay
What is the expected behavior?
No warnings or errors related to React 19's removal of element.ref access.
What is the current behavior?
The following error is thrown at runtime when GrapesJsStudio renders:
Accessing element.ref was removed in React 19. ref is now a regular prop.
It will be removed from the JSX Element type in a future release.
Environment:
@grapesjs/studio-sdk: 1.1.1
React: 19.x
Next.js: 16.x
If is necessary to execute some code in order to reproduce the bug, paste it here below:
import { GrapesJsStudio } from "@grapesjs/studio-sdk/react";
export default function Page() {
return <GrapesJsStudio />;
}
Code of Conduct
What browser are you using?
Firefox
Describe the bug
How to reproduce the bug?
Set up a React 19 project with @grapesjs/studio-sdk@1.1.1
Render the GrapesJsStudio component
Open the browser console or check the Next.js error overlay
What is the expected behavior?
No warnings or errors related to React 19's removal of element.ref access.
What is the current behavior?
The following error is thrown at runtime when GrapesJsStudio renders:
Accessing element.ref was removed in React 19. ref is now a regular prop.
It will be removed from the JSX Element type in a future release.
Environment:
@grapesjs/studio-sdk: 1.1.1
React: 19.x
Next.js: 16.x
If is necessary to execute some code in order to reproduce the bug, paste it here below:
Code of Conduct