fix: Explicitly import pdf worker entry to register global worker object #82
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
fufler
force-pushed
the
explicitly-import-worker
branch
2 times, most recently
from
f5759fa
to
94bac72
Compare
fufler
changed the title
fufler
force-pushed
the
explicitly-import-worker
branch
from
94bac72
to
e8ea711
Compare
|
Published as part of v1.7.5 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Latest pdfvuer version does not contain pdf worker. Thus demo page served by
npm run servedoes not work due to following errors:Describe the changes you have made in this PR -
This PR simply adds worker entry import to make worker globally accessible via
windowobject.Solved issue is probably related to #80.
Have you updated the readme?
No
Screenshots of the changes (If any) -
N/A