[Snyk] Upgrade url-toolkit from 1.0.9 to 2.1.6 #4
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
Snyk has created this PR to upgrade url-toolkit from 1.0.9 to 2.1.6. See this package in NPM: https://www.npmjs.com/package/url-toolkit See this project in Snyk: https://app.snyk.io/org/tjenkinson/project/0f2c6691-095b-445d-aa20-a192c8179421?utm_source=github&utm_medium=upgrade-pr
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.
Snyk has created this PR to upgrade url-toolkit from 1.0.9 to 2.1.6.
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.Warning: This is a major version upgrade, and may be a breaking change.
Release notes
Package name: url-toolkit
-
2.1.6 - 2018-08-31
-
2.1.5 - 2018-08-29
-
2.1.4 - 2018-01-26
- remove use of
-
2.1.3 - 2018-01-21
- Fix error when normalizing and relative url empty (#11)
-
2.1.2 - 2017-12-29
-
2.1.1 - 2017-03-28
-
2.1.0 - 2017-03-26
-
2.0.1 - 2017-03-05
-
2.0.0 - 2017-03-05
-
1.0.11 - 2017-02-23
-
1.0.10 - 2017-02-04
-
1.0.9 - 2017-02-04
from url-toolkit GitHub release notesNo content.
;is now allowed in fragments (#13)Previously
http://a.com/expiretime=111;dirmatch=true/master.m3u8+./a:bwould not be handled correctly.this(#12)Scheme regex is now a bit stricter.
It now must match
[a-zA-Z0-9+\-.]as described in the RFC.This means relative urls that happen to contain ‘:’ are more likely to be recognised as relative providing they contain a character that does not satisfy the above.
Also updated the README mentioning that if you know a URL is relative, you should prefix it with
./.Fix typescript types export
Adds typescript type definitions.
Fix bug in regex.
This should be backwards compatibile with version 1 if the
alwaysNormalizeoption is set totrue. This option is required as normalization should only be performed if necessary, according to the spec.The one exception is a combination like "http://a.com/b/cd?test=1#something" + ";x", which previously incorrectly being resolved as "http://a.com/b/;x", instead of "http://a.com/b/cd;x". To loose the last segment of the path the relative URL should be "./;x".
Handle base url protocol being '//'.
This was not working properly when the relative url started with '/' or '//'.
Commit messages
Package name: url-toolkit
Compare
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs