GrapesJS / GrapesJS/studio

BUG: element.ref deprecation warning thrown in React 19 with GrapesJsStudio component (v1.1.1)

Open
#29 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
No language data
Stars
11
Forks
3
PR merge metrics
No merged PRs in 30d

Description

### 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:
```js
import { GrapesJsStudio } from "@grapesjs/studio-sdk/react";

export default function Page() {
return ;
}
```

### Code of Conduct

- [x] I agree to follow this project's Code of Conduct

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.