forked from alvarcarto/url-to-pdf-api
-
Notifications
You must be signed in to change notification settings - Fork 0
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
Upgrade to latest version #2
Open
nprail
wants to merge
82
commits into
master
Choose a base branch
from
next
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
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
The motivation behind the switch from `pdf2json` to `pdf-parse` was that the former was not able to correctly read the PDF:s generated by the updated Chromium version. Looking at the GitHub issues of that project showed that it was quite buggy and not really maintained anymore. `pdf-parse` on the other hand had no problem with PDF parsing, so the choice was easy.
Depending on the OS, Skia seems to render spaces and hyphens. When running tests it introduces some incosistencies, so we normalize both non-breaking spaces and soft hyphens to respective regular spaces and hyphens.
Upgrade puppeteer to 1.14
This came about because after running npm install we see the following: found 39 high severity vulnerabilities run `npm audit fix` to fix them, or `npm audit` for details
The previous image is no longer maintained also it does not even point to the correct source! See this issue: microbox/node-url-to-pdf-api#4 We have built a new image that we will maintain also in the future as part for Restorecommerce.
…rabilities Fixes lodash vulnerabilities by updating to latest revision
add option to create a browser by connecting to a chrome websocket endpoint
Point to different docker Image that is actually maintained
Use env-cmd to load .env file
Adding browser executable path option
…ealthcheck-endpoint Add healthcheck endpoint
…rade Revert "Node upgrade"
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.
No description provided.