You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Attach (recommended) or Link to PDF file here: N/A
Configuration:
Web browser and its version: N/A
Operating system and its version: Mac OS
PDF.js version: Any
Is a browser extension: No
Steps to reproduce the problem:
N/A
What is the expected behavior? (add screenshot)
pdfjs-dist should have all required 3rd-party packages (including core-js) explicitly specified in the package.json dependencies.
What went wrong? (add screenshot)
If in the app a version of core-js mismatch the implicit expectation of the pdfjs-dist code in pdfjs-dist/lib/shared/compatibility.js, then it leads to unexpected behaviour or build errors, such as
Module not found: Error: Can't resolve 'core-js/es/string/starts-with'
Link to a viewer (if hosted on a site other than mozilla.github.io/pdf.js or as Firefox/Chrome extension):
N/A
The pull request is making it more clear that the /lib folder shouldn't be used for anything other than unit tests. For using PDF.js you should use the pre-built versions because core-js is a dev dependency and its references will be resolved on build time. Hence there should be no need to put core-js in the dependencies of pdfjs-dist.
Attach (recommended) or Link to PDF file here: N/A
Configuration:
Steps to reproduce the problem:
What is the expected behavior? (add screenshot)
pdfjs-dist should have all required 3rd-party packages (including core-js) explicitly specified in the package.json dependencies.
What went wrong? (add screenshot)
If in the app a version of
core-js
mismatch the implicit expectation of the pdfjs-dist code inpdfjs-dist/lib/shared/compatibility.js
, then it leads to unexpected behaviour or build errors, such asLink to a viewer (if hosted on a site other than mozilla.github.io/pdf.js or as Firefox/Chrome extension):
N/A
See similar issue parcel-bundler/parcel#2819 (comment)
The text was updated successfully, but these errors were encountered: