Console Error: Accessing element.ref was removed in React 19. ref is now a regular prop.

[michaelcychan]

Hello, we are reviewing your library and find it suitable for our needs.

Issue:
The PDF files can be loaded and displayed; however, I am encounter this 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.

Environment:

• React: 19.0.0
• Next.Js: 15.2.4
• @pdf-viewer/react: 1.2.0

I encounter the same issue from your Next.js example and have the same Console Error.

Do you have any workaround or any plans to fix it? Thank you very much!

[david-reactpdf]

@michaelcychan

Just echoing what I shared in my email (and posting here for anyone else following along): the warning you’re seeing about element.ref comes from a breaking change introduced in React 19:

Accessing element.ref was removed in React 19. ref is now a regular prop.

While not ideal, this doesn’t break functionality. We’ve tested React PDF with React 19, and everything still works as expected—so you can continue using the viewer without issue for now.

React PDF is still built with React 18 in mind, and full support for React 19 (including removing this warning) will likely require maintaining separate builds due to peer dependency differences. We’re actively monitoring adoption of React 19 and will align support in an upcoming release as it becomes more widespread in the ecosystem.

[xiaohanyu]

+1 for this warning.

Not sure whether there's way to suppress this warning.