Updating canvg version #2729
Closed
Updating canvg version #2729
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
|
Thanks for the PR. I will merge it as soon as I find the time. |
|
Thanks, I went with version 2.0.0 to avoid other breaking changes in 3.x. If I have time, I'll look at upgrading to 3.0.6 and will open another PR. |
|
Thanks. Since the next jsPDF will be a bigger release, this is a good chance to update to canvg 3.x. |
|
Closing this because with #2804 I updated to canvg 3.0. |
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.
This is to resolve a "high" level vulnerability (as reported by NPM) with the dependency chain that is:
jspdf > canvg > jsdom > request > hawk > cryptilesBased on the usage of Cangv in the project, there should not be any breaking changes introduced by this version change.