Error: Accessing element.ref was removed in React 19. ref is now a regular prop
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 183
- Forks
- 44
- PR merge metrics
- No merged PRs in 30d
Description
Error: 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.
at createUnhandledError (http://localhost:3000/next/static/chunks/node_modules_next_dist_client_523921..js:689:49)
at handleClientError (http://localhost:3000/next/static/chunks/node_modules_next_dist_client_523921..js:856:56)
at console.error (http://localhost:3000/next/static/chunks/node_modules_next_dist_client_523921..js:991:56)
at Object.elementRefGetterWithDeprecationWarning (http://localhost:3000/next/static/chunks/node_modules_next_dist_compiled_107ce8..js:1267:103)
at ia (http://localhost:3000/next/static/chunks/node_modules%40grapesjs_studio-sdk_dist_react_es_a7e039.js:4899:22)
at 1 (http://localhost:3000/next/static/chunks/node_modules%40grapesjs_studio-sdk_dist_react_es_a7e039.js:4850:24)
at Ee (http://localhost:3000/next/static/chunks/node_modules%40grapesjs_studio-sdk_dist_react_es_a7e039.js:4565:41)
at _e (http://localhost:3000/next/static/chunks/node_modules%40grapesjs_studio-sdk_dist_react_es_a7e039.js:4845:16)
at yO (http://localhost:3000/next/static/chunks/node_modules%40grapesjs_studio-sdk_dist_react_es_a7e039.js:9326:8)
at react-stack-bottom-frame (http://localhost:3000/next/static/chunks/node_modules_next_dist_compiled_react-dom_1f56dc..js:13403:24)
at renderWithHooks (http://localhost:3000/next/static/chunks/node_modules_next_dist_compiled_react-dom_1f56dc..js:2977:24)
at updateForwardRef (http://localhost:3000/next/static/chunks/node_modules_next_dist_compiled_react-dom_1f56dc..js:4638:21)
at beginWork (http://localhost:3000/next/static/chunks/node_modules_next_dist_compiled_react-dom_1f56dc..js:5421:24)
at runWithFiberInDEV (http://localhost:3000/next/static/chunks/node_modules_next_dist_compiled_react-dom_1f56dc..js:631:20)
at performUnitOfWork (http://localhost:3000/next/static/chunks/node_modules_next_dist_compiled_react-dom_1f56dc..js:7955:97)
at workLoopConcurrent (http://localhost:3000/next/static/chunks/node_modules_next_dist_compiled_react-dom_1f56dc..js:7951:58)
at renderRootConcurrent (http://localhost:3000/next/static/chunks/node_modules_next_dist_compiled_react-dom_1f56dc..js:7933:71)
at performWorkOnRoot (http://localhost:3000/next/static/chunks/node_modules_next_dist_compiled_react-dom_1f56dc..js:7565:175)
at performWorkOnRootViaSchedulerTask (http://localhost:3000/next/static/chunks/node_modules_next_dist_compiled_react-dom_1f56dc..js:8394:9)
at MessagePort.performWorkUntilDeadline (http://localhost:3000/next/static/chunks/node_modules_next_dist_compiled_107ce8..js:2353:64)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the warning in the Next.js app with React 19 and inspect the @grapesjs/studio-sdk stack entries, especially the ia, Ee, and _e paths. Trace the element.ref access to a repository entry point and verify the warning no longer appears; the issue names no source file or test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nextjs, react, typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100