react-Adobe-embed is a powerful and versatile React component that seamlessly integrates Adobe's document viewing and editing capabilities into your web applications. With this component, you can easily embed Adobe PDF documents, allowing users to view, interact with, and even sign them directly within your React application. The react-adobe-embed component is essentially a React Custom Component that wraps around Adobe's Embed API for PDFs.
- Removes need to interface with Adobe's Embed API and provides an easier way through React.js.
- Seamless integration of all Adobe's document viewing and editing capabilities with embed PDF documents
- Comprehensive CD/CI coverage with live heartbeat monitoring and integration testing of this custom React component to ensure that all capabilities are functional in real-time.
React-Adobe-Embed is built with reliability and robustness in mind. The component undergoes rigorous testing and monitoring to ensure its stability and performance. Through live heartbeat monitoring, both the React component and the external API service it relies on are continuously checked to detect any issues or anomalies. Additionally, the component is fully covered by standard integration testing, providing comprehensive CD/CI coverage. This ensures that any changes or updates to the codebase are thoroughly tested before being deployed, minimizing the risk of introducing bugs or regressions.
| Canary Hearbeat Status | Alarm on Code Push for React-Adobe-Embed | Integration/Unit Test on Code Push | Development Coding Effort | Package Ratings |
|
|
|
|
 |
Through live heartbeat monitoring the react component as well as the external api service used, as well as via standard integartion testing, that provides full CD/CI coverage of react-adobe-embed. Further details regarding CD to be provided.
Getting started with React-Adobe-Embed is quick and easy. The component can be installed via popular package managers such as npm and yarn:
npm install react-adobe-embedor
yarn add react-adobe-embedOnce installed, you can import the component into your React application and start using it right away. The component provides a simple and intuitive API for embedding Adobe documents and customizing the viewing experience.
You will need a clientId "key" from Adobe to use the Embed API and therefore this react-adobe-embed as well. You can get one for free (and create up to 20 keys) by visiting the Adobe Embed API Creation Page. Keys are tied to a specific domain that you specificy when creating a key, which means that the key only works for that domain, e.g. app.exampledomain.com, or example.com, or localhost. For you convenience, you may use the clientId show below in the example usages, but take note that it only works on http://localhost:80.
import React from "react";
import ReactViewAdobe from "react-adobe-embed";
const App = () => {
return (
<ReactViewAdobe
/**
* You can use the clientId below, since its setup for `http://localhost:80`
* In order to generate your own clientId that is set with a configured
* application domain,(e.g. yourappwithadobeembedstuff.com),
* visit: https://acrobatservices.adobe.com/dc-integration-creation-app-cdn/main.html?api=pdf-embed-api
*/
clientId="324caa2a91b84f688935436cd2d25217"
title="Bodea Brochure"
url={
"https://acrobatservices.adobe.com/view-sdk-demo/PDFs/Bodea%20Brochure.pdf"
}
/**
* This id must be unique to the pdf it is supposed to render,
* as part of requirements from adobe embed's api.
* If you do actually have multiple ReactViewAdobe components,
* and decide to use the same ID (even though you have different pdfs),
* you will end up see how the pdf that each component renders will
* all be the same pdf. The only time where you would use the
* same ID, is if you are using lightbox mode since for lightbox mode,
* pdf renders are full screen and only shown when triggered by
* some action on the page.
*/
id="pdf-brochure"
fileMeta={{
fileName: "Bodea Brochure",
}}
previewConfig={{
defaultViewMode: "FIT_WIDTH",
showAnnotationTools: false,
showPageControls: false,
showDownloadPDF: false,
}}
style={{
height: "50vh",
}}
/>
);
};- Example using React States
import React from 'react';
import ReactViewAdobe, {previewFile} from 'react-adobe-embed'
const App = () => {
const [viewDocumentTriggered, setViewDocumentTriggered] = React.useState(false);
return (
<div>
<button onClick={(e)=>{
e.preventDefault();
setViewDocumentTriggered(true);
previewFile({
clientID: "324caa2a91b84f688935436cd2d25217",
url: "https://acrobatservices.adobe.com/view-sdk-demo/PDFs/Bodea%20Brochure.pdf",
id: "exhbit-a-pdf",
fileMeta: {
fileName: "Bodea Brochure"
},
previewConfig: {
"embedMode": "LIGHT_BOX"
}
})
}}>
View Document
</button>
// Tip: Yes you need to have this component in Lightbox mode
// Tip 2: You can use the same ReactViewAdobe component below
// for one or more different buttons that each trigger a different pdf.
// Just make sure that the id used in the button's onClick function
// is also the same.
// Tip 3: Yes lightbox mode uses the element below to place the pdf rendering,
// and thus for full-screen to work best, make sure this element is at the top of the page,
// and not being contained within a parent element that might cause it to either be:
// 1. Not full screen (e.g. due to overflow hidden and width/heigth cutoffs)
// 2. Not visible (e.g. due to z-index)
// 3. Not able to be interacted with (e.g. due to pointer-events being none)
// Tip 4: https://linkedinliu.com uses lightbox mode for a number of different buttons which each trigger their own pdf. Check out the demo there and see possible ways to use lightbox mode.
// Bonus Tip: Checkout https://ziping.org/accolades to view a demo of the pdf rendering using
// in-line embed mode.
<ReactViewAdobe
id="exhbit-a-pdf"
style={{
height:0,
width:0
}}
clientId="324caa2a91b84f688935436cd2d25217"
title="Bodea Brochure"
embedMode="LIGHT_BOX"
fileMeta={{
fileName: "Bodea Brochure"
}}
url={"https://acrobatservices.adobe.com/view-sdk-demo/PDFs/Bodea%20Brochure.pdf"}
previewConfig={{
"embedMode": "LIGHT_BOX"
}}/>
</div>
)
}- More Lightbox example code without using React States, and through calling adobe embed api directly.
- View a deployed demo here.
You can also load this as a CDN script via jsdelivr through their version aliased delivery here. Also, the latest version can be accessed publically through the CD workflow as well, at ziping-liu-corporation.github.io/react-adobe-embed/dist/react-adobe-embed.cdn.js.
For now this CDN bundle is only accessible in the form of a UMD bundle, through a global named
ReactViewAdobe(and accessible viawindow.ReactViewAdobe) that provides access to the default export fromreact-adobe-embedpackage, or also known by its name as a named exportReactViewAdobe.
<head>
<script
crossorigin
src="https://unpkg.com/react@18/umd/react.development.js"
></script>
<script
crossorigin
src="https://unpkg.com/react-dom@18/umd/react-dom.development.js"
></script>
</head>
<body>
<h1>My PDF Viewer</h1>
<div id="root"></div>
<script src="https://cdn.jsdelivr.net/npm/react-adobe-embed/lib/bundle.js"></script>
<script>
/**
* @type {React} ReactCDN
* In order to use the react-adobe-embed
* component library, you also need
* to have loaded React and ReactDOM
* via CDN as well. This is usually done
* via a script tag that would be placed before
* the script tag for react-adobe-embed's cdn.
* Although the script tags run
* asynchronously, they are still ran
* in the order in which they appear
* within the html file. Ideally, you would place
* the script tag for React and ReactDOM CDN's
* in the "head" portion of the html file,
* while the script tag for react-adobe-embed CDN
* is placed at the end of the "body" portion
* of the html file.
* This ensures that the React and
* ReactDOM CDN's are loaded before
* react-adobe-embed. CDN links for React
* and ReactDOM can be found via React's doc site:
* https://legacy.reactjs.org/docs/cdn-links.html
*/
const ReactCDN = window.React;
/**
* @type { import('react-dom/client') }
*/
const ReactDOMCDN = window.ReactDOM;
/**
* @type {import('react-adobe-embed').default}
* ReactViewAdobe custom component library
* loaded via CDN from the above script tag
* via jsdelivr.net
*/
const ReactViewAdobeCDN = window.ReactAdobeEmbed.ReactViewAdobe;
/**
* @type { import('react-adobe-embed').ReactViewAdobeProps }
*/
const myReactViewAdobeProps = {
clientId: "324caa2a91b84f688935436cd2d25217",
url:
"https://raw.githubusercontent.com/" +
"ZipingL/dna/main/23andMe_Ancestry_Book.pdf",
style: {
height: "600px",
width: "100%",
},
fileMeta: {
fileName: "23andMe Ancestry Book",
},
};
const CreatedReactComponent = ReactCDN.createElement(
ReactViewAdobeCDN,
myReactViewAdobeProps,
null,
);
const rootElement = document.getElementById("root");
if (rootElement) {
const ReactRootFromElement = ReactDOMCDN.createRoot(rootElement);
ReactRootFromElement.render(CreatedReactComponent);
}
</script>
</body>- Another example of loading
react-adobe-embedand utilizing it as a cdn is currently part of the testing endpoint used as part of the continuous integration workflow that is active for this package.- The testing endpoint code can be viewed at canary/routes/CDN.tsx
- The deployed testing endpoint code can be viewed at ziping-liu-corporation.github.io/#/cdn
Note: these other steps below are no longer required but remain to provide insight on how react-adobe-embed handles adobe embed api
2.As the current implementation of creating LIGHT_BOX embed pdf's is quite complicated, you can view a live code example of how to use LIGHT_BOX mode with react-adobe-embed here
- You don't need to worry about handling outside script tags. The react wrapper handles any script downloading. Simple call the React Component as shown above.
In the past it was this:<script src='https://documentcloud.adobe.com/view-sdk/main.js'></script>as instructed by their office docs.
If you use this URL right now however: it will give you an error saying to update your PDF Viewer. I saw the error on Nov 28th myself and asked myself... This is an embed PDF viewer, i shouldn't need to update anything.Anyways, the URL has been updated above in step 1.Since I guess Adobe just likes to change the URL to whatever they want, you can find the correct URL to use to include their ADOBE MAGIC STUFF here.- I don't know why but the folks at Adobe decided to change the script URL, and then also change the global variable name used to store the Adobe api methods, this has ulimately caused this npm package as actually a broken useless wrapper... so why didn't anyone add to the discussion board to let me know? Seriously? Just literally next time say, hey idiot your code is broken. I won't be offended. It's just code dude.
Cannot read properties of undefined (reading 'View')- Remedy: disable ReactStrictMode when rendering the React Application, e.g., remove <React.StrictMode>
LicenseVerificationService.js:32 POST https://viewlicense.adobe.io/viewsdklicense/jwt 401 (Unauthorized)(The pdf renders then immediately disappears for no apparent reason)- Remedy: the provided clientId is invalid. This is mainly due to the clientId provided not setup to allow for adobe embed api calls at the current hostname. You are free to use the clientId, `` shown in the example above, but take note that you will need to run your app on localhost port 80. To create your own clientId, visit the official page here for react adobe embed.
Given the increasing intricacy of this wrapper, it is imperative to safeguard the fundamental functionality from any potential disruption caused by new code alterations. At present, a rudimentary examination is conducted to verify the wrapper's capability to accurately display the PDF content while effectively handling asynchronous requests to the Adobe PDF Embed API.
This test runs as a github action whenever a code change occurs. Note, these tests only test the react code within, and thus mocks out any calls to adobe's embed api service.
npm run test
PASS src/__tests__/base.test.tsx
BasicRender
✓ should render the component (23 ms)
✓ should re-render the component when component props updated (18 ms)
Test Suites: 1 passed, 1 total
Tests: 2 passed, 2 total
Snapshots: 2 passed, 2 total
Time: 1.699 s
Ran all test suites.The end to end tests which includes testing of the react-adobe-embed react component and the proper usage and response from the adobe embed api service is handled in a seperate repository, react-adobe-embed-cd-canary.
- These tests are deployed as a form of heartbeat or canary testing via github workflows.
- These tests are also ran with each new code push within this repo, and are triggered via a respitory dispatch event
Note: Further details including the testing architecture that allows for then a continuous dpeloyment and integartion of the react-adobe-embed component will be added. Please see the FAQs below
- This has been fixed with the latest major version update to version 12.0.0. The package.json had been updated to correctly point to where type definitions exist.
- No doubt, the package and component is now pretty complicated in terms of the amount of code and directories and features it provides, which can definitely make it difficult to understand the basic usage or even the purpose of the package. The readme is intended to be concise such that it allows for a quick understanding of the most important aspects of the package. As of now a more detailed wiki page is being worked and will be provided as an additional resource that provides detailed explainations and guidance on the code and package.
- Yes, please see linkedinliu.com, which uses
react-adobe-embedto render and display PDF's.
- You can create a new discussion post since they are open to the public
- Or simply open up a pull request or issue, it can be for any reason there's no required level of issue.
- Yes, since this wrapper is actrively used in LIU LLC Sites, it is being updated and expect more updates and stuff on it
- In some cases it is overkill, so hence you may utilize Adobe Embed API that is the service, hence why this package is called a wrapper and not ADOBE API Library
This wrapper is overkill as a package on npm, a four year old could just write this out inline on any react front-end website
- We agree, this is for those who are younger than four years old and not yet able to inline out components as vanilla react-js
, is a pretty decent way to view the NPM releases, or perhaps you might find
more useful.
Adobe, with its renowned symbols such as Acrobat, the Adobe PDF insignia, Adobe Premiere, Creative Cloud, InDesign, and Photoshop, are acknowledged trademarks of Adobe, registered in the United States and/or other jurisdictions. Ziping Liu Corporation, a trademark registered in the United States, and LIU LLC, incorporated under the laws of the State of Texas, are also part of our respected portfolio. At this moment, we have no additional public declarations to make or inquiries to address on this matter.
Ziping LIU Corporation, overseeing Adobe code, is proud to unveil an innovative Nested React Component, aptly named 'ReactViewAdobe'. This component is a result of careful engineering, designed with the specific aim of managing the API calls and configurations associated with the Adobe Embed API SDK. This component, in its profound wisdom, employs React Hooks, thereby transforming what the Adobe Embed API SDK perceives as static and unadorned JavaScript code into an elegantly transposed representation in the Document Object Model (DOM). This is a testament to our commitment to innovation and growth in the ever-evolving digital landscape, or alternatively, necessary code scaffolding to allow for Adobe's complex API to function properly in modern frameworks.