react-pdf breaking changes
Every breaking API change we have recorded in react-pdf on npm: 29 breaking changes in 1 version. Below are its newest version, removals and renames first, each with its source.
Newest change September 10, 2026

On this page
11.0.0
- Removed
React-PDF requires Node.js 22.13.0 or newer. github.com - Removed
Minimum browser requirements are now Chrome 125 and Safari 18 (iOS 18). Older browsers may need polyfills or transpilation. github.com - Removed
React 19 or later is now required. Upgrade react and react-dom to version 19. github.com - Removed
CMapReaderFactory
Replace custom implementations with a single BinaryDataFactory whose fetch({ kind, filename }) method handles all resource types. Setting cMapUrl alone needs no change. github.com - Removed
PDFDocumentProxy.destroy
If you manage PDF.js documents yourself, destroy the loading task instead. github.com - Removed
pdfjs.getDocument
Remove the length option if you supplied it to pdfjs.getDocument. The length argument of PDFDataRangeTransport remains supported. github.com - Removed
StandardFontDataFactory
Replace custom implementations with a single BinaryDataFactory whose fetch({ kind, filename }) method handles all resource types. Setting standardFontDataUrl alone needs no change. github.com - Removed
WasmFactory
Replace custom implementations with a single BinaryDataFactory whose fetch({ kind, filename }) method handles all resource types. Setting wasmUrl alone needs no change. github.com - Behavior changed
Document
Document, Page, Thumbnail and Outline now use boundary fallbacks for loading and failures. Set suspense={false} on Document to keep the previous loading and error props. github.com - Behavior changed
onRenderAnnotationLayerSuccess
onRenderAnnotationLayerSuccess runs after annotation rendering finishes. Read rendered annotation elements in that callback, and handle failures in onRenderAnnotationLayerError. github.com
And 19 more in this version.
Check your code
These are the changes. To see which of them reach your code, scan a public repository, or have your coding agent call check_code with your manifest or lockfile over MCP. The API reads every change in every version, not only the newest. On Team and up, a fix pull request opens for the changes that reach a connected repository. Nothing merges or deploys.

Put your code on continuous management.
Scan a public repository now, or give your agent one line.
See how out of date your code is.
Tell your agent what changed since it was trained.
claude mcp add --transport http since https://api.since.dev/mcp