@progress/kendo-react-pdf-viewer
Advanced tools
Weekly downloads
Readme
Important
- This package is а part of KendoReact—a commercial UI library.
- You will need to install a license key when adding the package to your project. For more information, please refer to the KendoReact My License page.
- To receive a license key, you need to either purchase a license or register for a free trial. Doing so indicates that you accept the KendoReact License Agreement.
- The 30-day free trial gives you access to all the KendoReact components and their full functionality. Additionally, for the period of your license, you get access to our legendary technical support provided directly by the KendoReact dev team!
Start using KendoReact and speed up your development process!
The React PDFViewer library, part of KendoReact, allows users to view and interact with PDF files directly in the browser, without needing to download the file or use third-party tools or browser extensions.
Among the features which the KendoReact PDFViewer component delivers are:
For any issues you might encounter while working with the KendoReact PDFViewer, use any of the available support channels:
High-level component overview pages
Copyright © 2023 Progress Software Corporation and/or its subsidiaries or affiliates. All Rights Reserved.
Progress, Telerik, and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries.
FAQs
KendoReact PDFViewer package
The npm package @progress/kendo-react-pdf-viewer receives a total of 541 weekly downloads. As such, @progress/kendo-react-pdf-viewer popularity was classified as not popular.
We found that @progress/kendo-react-pdf-viewer demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket installs a Github app to automatically flag issues on every pull request and report the health of your dependencies. Find out what is inside your node modules and prevent malicious activity before you update the dependencies.