react-adobe-embed - npm Package Compare versions

Comparing version 11.2.9 to 11.2.10

package.json

 {
   "name": "react-adobe-embed",
-  "version": "11.2.9",
+  "version": "11.2.10",
   "homepage": "https://ziping-liu-corporation.github.io/react-adobe-embed/#/home",
@@ -64,2 +64,3 @@ "repository": {
   "files": [
+    "LICENSE",
     "lib",
@@ -76,3 +77,3 @@ "dist",
     "test": "jest",
-    "build:canary": "npm run build:roll:canary && rsync -rhv --progress ./public/* ./build && rsync -rhv --progress README.md ./build && npm run build:roll:cdn && rsync -rhv --progress ./dist ./build/ && npm run build:public",
+    "build:canary": "npm run build:roll:canary && rsync -rhv --progress ./public/* ./build && cp ./README.md ./build && npm run build:roll:cdn && rsync -rhv --progress ./dist ./build/ && cp ./LICENSE ./build && npm run build:public",
     "build:public": "node ./scripts/public.js",
@@ -88,4 +89,4 @@ "build:roll:canary": "rimraf lib && rollup --bundleConfigAsCjs -c rollup.config.canary.js",
   },
-  "author": "Ziping Liu <[e-mail]> (https://jeffbezos.academy)",
-  "license": "MIT HUTTENLOCHER WHAT ARE YOU DOING BOARD OF DIRECTOR AT AMAZON?",
+  "author": "Ziping Liu <[e-mail]>",
+  "license": "LicenseRef-LICENSE",
   "devDependencies": {
@@ -122,3 +123,2 @@ "@babel/core": "^7.23.2",
     "babel-plugin-module-resolver": "^5.0.0",
-    "core-js": "^3.33.1",
     "cssnano": "^6.0.1",
@@ -148,7 +148,4 @@ "eslint": "^8.52.0",
     "ts-loader": "^9.4.1",
-    "ts-node": "^10.9.1",
-    "tslib": "^2.4.1",
     "typescript": "^4.9.5",
     "webpack": "^5.75.0",
-    "webpack-bundle-analyzer": "^4.8.0",
     "webpack-cli": "^5.0.0",
@@ -155,0 +152,0 @@ "webpack-dev-server": "^4.11.1"

README.md

@@ -22,6 +22,6 @@ # [React based ADOBE PDF EMBED API Component Facade](https://ziping-liu-corporation.github.io/react-adobe-embed/) is a Great Tool for Displaying PDF's with rich features,
       title="Unit Test that is a quick check of code changes via mocking out the very large external react embed api spaghetti code"
-      href="https://github.com/ZIPING-LIU-CORPORATION/react-adobe-embed/blob/slave/README.md#integration-testing">Integration/Unit Test on Code Push</a>
+      href="#integration-testing">Integration/Unit Test on Code Push</a>
     </td>
     <td>
-      <a href="http://www.wakatime.com/@aws">Development Coding Effort</a>
+      <a href="https://www.wakatime.com/@aws">Development Coding Effort</a>
     </td>
@@ -32,9 +32,10 @@ </tr>
    <td>
-  <a href="https://cloud.cypress.io/projects/izghdg/runs">  <img title="Canary heartbeat status check for deployed latest component and adobe pdf api availability" src="https://github.com/ZIPING-LIU-CORPORATION/react-adobe-embed-cd-canary/actions/workflows/cypress-canary.yaml/badge.svg"/> </a>
+  <a href="https://github.com/ZIPING-LIU-CORPORATION/react-adobe-embed-cd-canary/actions/workflows/cypress-canary.yaml">  <img title="Canary heartbeat status check for deployed latest component and adobe pdf api availability" src="https://github.com/ZIPING-LIU-CORPORATION/react-adobe-embed-cd-canary/actions/workflows/cypress-canary.yaml/badge.svg"/> </a>
    </td>
    <td>
-     <img src="https://github.com/ZIPING-LIU-CORPORATION/react-adobe-embed/actions/workflows/canaryapp.yml/badge.svg">
+   <a href="https://github.com/ZIPING-LIU-CORPORATION/react-adobe-embed/actions/workflows/canaryapp.yml">
+     <img src="https://github.com/ZIPING-LIU-CORPORATION/react-adobe-embed/actions/workflows/canaryapp.yml/badge.svg"> </a>
    </td>
     <td>
-     <img src="https://github.com/ZIPING-LIU-CORPORATION/react-adobe-embed/actions/workflows/main.yml/badge.svg"/>
+     <a href="https://github.com/ZIPING-LIU-CORPORATION/react-adobe-embed/actions/workflows/main.yml"><img src="https://github.com/ZIPING-LIU-CORPORATION/react-adobe-embed/actions/workflows/main.yml/badge.svg"/></a>
     </td>
@@ -141,17 +142,2 @@ <td>
 
-<blockquote> 
-   
-*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](https://acrobatservices.adobe.com/view-sdk-demo/index.html#/view/LIGHT_BOX/Bodea%20Brochure.pdf) 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](https://codesandbox.io/p/sandbox/react-adobe-embed-pdf-galleria-showcase-yq5zz6?file=%2Fsrc%2FSections%2FMain.tsx%3A65%2C79)
-
-#### ~~3. Note on adobe sdk `<script>` tag:~~
- - 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](https://developer.adobe.com/document-services/docs/overview/pdf-embed-api/).~~
-  - 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](https://github.com/ZIPING-LIU-CORPORATION/react-adobe-embed/discussions/1) 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.
-</blockquote>
-
-
 ## Installation via CDN
@@ -241,3 +227,15 @@ You can also load this as a CDN script via [jsdelivr using this link](https://cdn.jsdelivr.net/npm/react-adobe-embed@11.2/dist/react-adobe-embed.cdn.js). By default 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](https://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 `ReactAdobeEmbed` that provides access to the default export from react-adobe-embed, or also known by its name as a named export `ReactViewAdobe`. Below is a sample html file that renders a PDF via react-adobe-embed loaded as a CDN.
 
+<blockquote> 
+   
+*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](https://acrobatservices.adobe.com/view-sdk-demo/index.html#/view/LIGHT_BOX/Bodea%20Brochure.pdf) 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](https://codesandbox.io/p/sandbox/react-adobe-embed-pdf-galleria-showcase-yq5zz6?file=%2Fsrc%2FSections%2FMain.tsx%3A65%2C79)
 
+#### ~~3. Note on adobe sdk `<script>` tag:~~
+ - 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](https://developer.adobe.com/document-services/docs/overview/pdf-embed-api/).~~
+  - 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](https://github.com/ZIPING-LIU-CORPORATION/react-adobe-embed/discussions/1) 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.
+</blockquote>
 
@@ -244,0 +242,0 @@ ## Troubleshooting common errors

New alerts

Mixed license

License

(Experimental) Package contains multiple licenses.

Found 1 instance in 1 package

Non-permissive License

License

(Experimental) A license not known to be considered permissive was found

Found 1 instance in 1 package

Unidentified License

License

(Experimental) Something that seems like a license was found, but its contents could not be matched with a known license

Found 1 instance in 1 package

Fixed alerts

No License Found

License

(Experimental) License information could not be found

Found 1 instance in 1 package

Improved metrics

Total package byte prevSize

91243

increased by0.77%

Dev dependency count

58

decreased by-6.45%

Number of package files

31

increased by3.33%

Worsened metrics

Number of low license alerts

3

increased by200%

License quality

80

decreased by-20%

Number of lines in readme file

309

decreased by-0.64%

No dependency changes