Update tus-js-client to v2.3.2 #194
Open
Conversation
This file contains hidden or 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
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 PR upgrades the tus-js-client dependency from v1 (whose last release was ~6 years ago) to v2. v2 is not the most up-to-date version of tus-js-client but not as old as its last release (2.3.2) was about 2 years ago. You can find a list of breaking changes in the accompanying blog post, but all of them seem to be irrelevant for tus-js-client.
I also considered upgrading to v4, but since v3 tus-js-client does not Node < 12 anymore, which is explicitly supported by vimeo.js according to its
package.json:vimeo.js/package.json
Lines 46 to 48 in ef0771e