Update dependency uuid to version 9

[MagicFame]

Hello ✋,

There is an active pull request for the update of the dependency uuid to version 9.
It is not a breaking change and it is a good idea to merge it because it creates an error to merge the vis-timeline project.

🔗 visjs/vis-timeline#1518

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: vis-data@7.1.4
npm ERR! Found: uuid@9.0.0
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 vis-data@7.1.4
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: uuid@8.3.2
npm ERR! node_modules/uuid
npm ERR!   peer uuid@"^7.0.0 || ^8.0.0" from vis-data@7.1.4
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-10-10T14_38_12_681Z-debug-0.log

[cjolif]

Is there any plan to merge that PR and get that security warning removed?

[Thomaash]

Update to version 9 is now allowed so you can install it in your project manually. However #982 is a breaking change as it removes IE11 support so for now we'll keep shipping v8 in the standalone bundle.