chore(deps): update dependency uuid to v9

[renovate[bot]]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
uuid	^7.0.0 || ^8.0.0 -> ^7.0.0 || ^8.0.0 || ^9.0.0
uuid	8.3.2 -> 9.0.0

---

Release Notes

uuidjs/uuid

v9.0.0

Compare Source

⚠ BREAKING CHANGES

• Drop Node.js 10.x support. This library always aims at supporting one EOLed LTS release which by this time now is 12.x which has reached EOL 30 Apr 2022.

• Remove the minified UMD build from the package.

  Minified code is hard to audit and since this is a widely used library it seems more appropriate nowadays to optimize for auditability than to ship a legacy module format that, at best, serves educational purposes nowadays.

  For production browser use cases, users should be using a bundler. For educational purposes, today's online sandboxes like replit.com offer convenient ways to load npm modules, so the use case for UMD through repos like UNPKG or jsDelivr has largely vanished.

• Drop IE 11 and Safari 10 support. Drop support for browsers that don't correctly implement const/let and default arguments, and no longer transpile the browser build to ES2015.

  This also removes the fallback on msCrypto instead of the crypto API.

  Browser tests are run in the first supported version of each supported browser and in the latest (as of this commit) version available on Browserstack.

Features

• optimize uuid.v1 by 1.3x uuid.v4 by 4.3x (430%) (#​597) (3a033f6)
• remove UMD build (#​645) (e948a0f), closes #​620
• use native crypto.randomUUID when available (#​600) (c9e076c)

Bug Fixes

• add Jest/jsdom compatibility (#​642) (16f9c46)
• change default export to named function (#​545) (c57bc5a)
• handle error when parameter is not set in v3 and v5 (#​622) (fcd7388)
• run npm audit fix (#​644) (04686f5)
• upgrading from uuid3 broken link (#​568) (1c849da)

build

• drop Node.js 8.x from babel transpile target (#​603) (aa11485)

• drop support for legacy browsers (IE11, Safari 10) (#​604) (0f433e5)

• drop node 10.x to upgrade dev dependencies (#​653) (28a5712), closes #​643

8.3.2 (2020-12-08)

Bug Fixes

• lazy load getRandomValues (#​537) (16c8f6d), closes #​536

8.3.1 (2020-10-04)

Bug Fixes

• support expo>=39.0.0 (#​515) (c65a0f3), closes #​375

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• [ ] If you want to rebase/retry this PR, click this checkbox.

---

This PR has been generated by Mend Renovate. View repository job log here.

[renovate[bot]]

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/uuid
npm ERR!   dev uuid@"9.0.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer uuid@"^7.0.0 || ^8.0.0" from [email protected]
npm ERR! node_modules/vis-data
npm ERR!   dev vis-data@"7.1.4" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/uuid
npm ERR!   peer uuid@"^7.0.0 || ^8.0.0" from [email protected]
npm ERR!   node_modules/vis-data
npm ERR!     dev vis-data@"7.1.4" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate-cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate-cache/others/npm/_logs/2022-11-08T06_29_37_405Z-debug-0.log

[vis-bot]

:tada: This PR is included in version 6.0.4 :tada:

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot :package::rocket: