[Snyk] Upgrade tus-js-client from 2.3.2 to 3.0.1

[azhavoro]

This PR was automatically created by Snyk using the credentials of a real user.

Snyk has created this PR to upgrade tus-js-client from 2.3.2 to 3.0.1.

ℹ️ 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.

• The recommended version is 3 versions ahead of your current version.
• The recommended version was released a month ago, on 2022-09-09.

Release notes

Package name: tus-js-client

• 3.0.1 - 2022-09-09
  

  What's Changed

  • Fix Cannot call a namespace error by @ aduh95 in #458
  • Require to use extensions in import specifiers by @ aduh95 in #459
  • Update many dependencies

  New Contributors

  • @ aduh95 made their first contribution in #458

  Full Changelog: v3.0.0...v3.0.1

• 3.0.0 - 2022-08-03
  

  This major release contains many features and bug fixes but also breaking changes! Please see the blog post for details.

• 3.0.0-0 - 2022-06-07
  

  3.0.0-0

• 2.3.2 - 2022-05-31
  

  What's Changed

  • Bump many dependencies
  • Make DetailedError extends Error in types by @ vkrol in #329
  • Export DetailedError from package by @ vkrol in #327

  New Contributors

  • @ vkrol made their first contribution in #328

  Full Changelog: v2.3.1...v2.3.2

from tus-js-client GitHub release notes

Commit messages

Package name: tus-js-client

• 20546a2 3.0.1
• aed3e84 require to use extensions in import specifiers (screencast links broken #459)
• f07ed8e Bump @ babel/preset-env from 7.18.10 to 7.19.0 (Save the lock object property in the database #461)
• 03631a9 Bump jasmine from 4.3.0 to 4.4.0 (How can I convert cvat dump annoation format to yolo or to coco or to pascal voc ? #462)
• d2fa4dd Bump eslint-plugin-react from 7.30.1 to 7.31.8 (Fix failed python install of testing environment #460)
• 22a7234 Fix `Cannot call a namespace` error ([WIP] adding https guide to installation guide #458)
• 754eca6 Bump puppeteer from 16.1.0 to 17.1.3 (CVAT new UI #464)
• fbf393a Bump eslint-plugin-react from 7.30.1 to 7.31.7 (Fixed bounding box ratio 1/3 #456)
• 5fc33e3 Bump uglify-js from 3.16.3 to 3.17.0 (Installation guide #444)
• dd2c16a Bump tsd from 0.22.0 to 0.23.0 (Fixed JS syntax #449)
• a099309 Bump @ babel/core from 7.18.10 to 7.19.0 (Building Docker with dextr fails with 503 Error #457)
• 14c3634 Phrase docs for chunkSize more strongly /cc @ Murderlon
• 6be06f6 Improve documentation for storeFingerprintsForResuming
• b03fac5 Remove non-existing callback argument for terminate
• 54f7406 Bump puppeteer from 15.5.0 to 16.1.0 (Fixed incorrect width of shapes borders in some cases #441)
• 52d9693 Add information about bundle sizes
• 99506d6 Fix link to v3 blog post
• 2b567c4 3.0.0
• 463d61d Update README
• bafe931 Rename HttpStack to DefaultHttpStack (Added updated guide and images #241)
• 169b099 Add parallelUploadBoundaries option (Re-Identification application #299)
• cc21778 Improve documentation for chunkSize
• 72c91c4 Support parallelUploads with fs.ReadStream
• f36640a fixup! Do not close source for abort, but for onSuccess

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

[bsekachev]

@klakhov Do you think we can update tus?

[klakhov]

@bsekachev let me check if everything works correctly after update

[klakhov]

/check

[github-actions]

✔️ All checks completed successfully
📄 See logs here

[nmanovic]

@klakhov , should we update the lock file?

[sizov-kirill]

There is no any vulnerabilities, so I guess we can close this PR.
The reason why Snyk sent this PR is "Upgrade out-of-date dependency" option that was enabled for our repository.
I think that updating dependencies without any vulnerabilities is unnecessary so I disabled this option and expect that we won't receive such PRs in future.

[klakhov]

/check

[github-actions]

❌ Some checks failed
📄 See logs here

[klakhov]

@bsekachev Could you look on failing test with multi-tasks? Do we need to merge develop to avoid this?

[bsekachev]

@klakhov

Looks like timeout issue. It is not related with this patch. Just bad connection with GitHub..

[klakhov]

Then I think we can merge this, tested locally, didn't meet any issues