Skip to content

Conversation

@L04DB4L4NC3R
Copy link
Member

Snyk has created this PR to upgrade react-pdf from 5.0.0 to 5.1.0.

merge advice
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 2 versions ahead of your current version.
  • The recommended version was released a month ago, on 2020-12-11.
Release notes
Package name: react-pdf
  • 5.1.0 - 2020-12-11

    What's new?

    • Added React 17 compatibility
    • Updated pdf.js to 2.5.207 (#686, #687).
  • 5.1.0-beta - 2020-11-23

    What's new?

    • Added React 17 compatibility
    • Updated pdf.js to 2.5.207 (#686, #687).
  • 5.0.0 - 2020-08-27

    ❗️ = breaking change

    What's new?

    • ❗️ React-PDF now ships with ES6 Modules along with CommonJS modules. This allows for Webpack and other bundlers to optimize your code better.
    • Updated pdf.js from 2.1.266 to 2.4.456. Thanks, @ kylemellander!

    What's changed?

    • ❗️ Internet Explorer 11 is no longer supported.
    • ❗️ Removed renderAnnotations backwards compatibility (#431).
    • ES6 builds of pdf.js are now used since Internet Explorer 11 support was dropped anyway.
    • Changed the way PDFDataRangeTransport is imported.
    • Explicitly initialize an EventBus instance (#593). Thanks, @ danieltott!

    Bug fixes

    • Fixed memory leak after unmounting Document (#452, #505). Thanks, @ oze4!
    • Fixed error, loading, noData propTypes not accepting functions (#579).
    • Fixed PDF rendering incorrectly if wrapped in an element with dir="rtl" (#588).
    • Added null check before calling destroy() method on loadingTask.
from react-pdf GitHub release notes

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants