-
Notifications
You must be signed in to change notification settings - Fork 10k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
core-js placed in dev-dependencies instead of dependencies #8890
Comments
Note that So, in closing, it's not really clear to me that any changes need to be made here. (Especially since the files found in https://github.com/mozilla/pdf.js/tree/master/src aren't really intended to be used as-is, without building them first.) |
Thanks for your reply. So does it mean using /display/svg.js is not recommended and there is another way of making SVG rendering using built version of PDF.js files? I tried to follow sample file as close as possible. Not sure if that changes anything, but I actually don't go to pdf.js/src, I'm importing the file from pdfjs-dist/lib. |
The https://github.com/mozilla/pdfjs-dist/tree/master/lib folder mostly exists in order to support unit-testing with Travis (using Node.js). |
Oh, I wasn't aware it's already there. Works like a charm. PS. Amazing work! Super excited for what will come :) |
In shared/compatibility.js, we have require() pointed at
core-js/fn/typed/uint8-clamped-array
.I can see that in pdf.js's package.json core-js is defined, but in devDependencies -
"core-js": "^2.5.0",
.When using this library somewhere, installing it via npm's pdfjs-dist, devDependencies are obviously not being installed. Thus, attempting to load shared/compatibility.js or any library that relies on shared/compatibility.js (i.e. shared/util.js) will fail.
The text was updated successfully, but these errors were encountered: