Replies: 3 comments
-
I'm getting the same error using ref |
Beta Was this translation helpful? Give feedback.
0 replies
This comment was marked as off-topic.
This comment was marked as off-topic.
-
@gagzu It looks like this is still an active upstream issue → mui/mui-x#13072 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Link to the code that reproduces this issue
https://github.com/gagzu/nextjs-issue-link-component-example
To Reproduce
To reproduce the error:
yarn install
yarn dev
Current vs. Expected behavior
The error I'm getting is: "Accessing element.ref was removed in React 19." The error is due to the Link component using
forwardRef
.The expected result is: Not seeing any error in the console.
Provide environment information
information about my environment: Operating System: Platform: linux Arch: x64 Version: #135~20.04.1-Ubuntu SMP Mon Oct 7 13:56:22 UTC 2024 Available memory (MB): 15871 Available CPU cores: 4 Binaries: Node: 20.9.0 npm: 10.1.0 Yarn: 1.22.22 pnpm: N/A Relevant Packages: next: 15.0.4-canary.13 // Latest available version is detected (15.0.4-canary.13). eslint-config-next: 15.0.3 react: 19.0.0-rc.1 react-dom: 19.0.0-rc.1 typescript: 5.6.3 Next.js Config: output: N/A
Which area(s) are affected? (Select all that apply)
Navigation
Which stage(s) are affected? (Select all that apply)
next dev (local), next start (local)
Additional context
No response
Beta Was this translation helpful? Give feedback.
All reactions