use exactly version 5.0.5 of vis-util

[Ryan1729]

As mentioned in this comment on #1064, the upstream package vis-util has removed the add/remove event listeners API in visjs/vis-util#1417, in version 5.0.6 specifically.

This causes errors to be displayed in the console when the user lets go of the mouse button after dragging the graph, including in the official examples.

Uncaught TypeError: (void 0) is not a function

This PR changes the package.json to use exactly 5.0.5 of vis-util; the newest version before the removal of the listeners API.

With this change, npm install unfortunately prints this resolution error:

npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: vis-graph3d@0.0.0-no-version
npm error Found: component-emitter@2.0.0
npm error node_modules/component-emitter
npm error   dev component-emitter@"2.0.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer component-emitter@"^1.3.0" from vis-util@5.0.5
npm error node_modules/vis-util
npm error   dev vis-util@"5.0.5" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.

Running npm install --force overrides this and allows the installation to complete.

After that, doing a build produces a vis-graph3d.min.js file that doesn't produce that Uncaught TypeError anymore.

[vis-bot]

🎉 This issue has been resolved in version 6.0.8 🎉

The release is available on:

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

Your semantic-release bot 📦🚀