chore: upgrade visx

[lilykuang]

SUMMARY

• After #23145, the follow error was introduce

Not Found - GET https://registry.npmjs.org/@vx/tooltip/-/tooltip-0.0.140.tgz - Not found
'@vx/tooltip@https://registry.npmjs.org/@vx/tooltip/-/tooltip-0.0.140.tgz' is not in this registry.

This pr is for upgrading visx to fix the error

BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TESTING INSTRUCTIONS

ADDITIONAL INFORMATION

• [ ] Has associated issue:
• [ ] Required feature flags:
• [ ] Changes UI
• [ ] Includes DB Migration (follow approval process in SIP-59)
  • [ ] Migration is atomic, supports rollback & is backwards-compatible
  • [ ] Confirm DB migration upgrade and downgrade tested
  • [ ] Runtime estimates and downtime expectations provided
• [ ] Introduces new feature or API
• [ ] Removes existing feature or API

[github-actions[bot]]

@TheCukitoDev, the latest version of Bun is v1.1.26, but this crash was reported on Bun v1.1.25.

Are you able to reproduce this crash on the latest version of Bun?

bun upgrade

[TheCukitoDev]

No it is not the error. I upgraded and now I have this:

WSL Kernel v5.15.153 | glibc v2.38
CPU: sse42 popcnt avx avx2
Args: "/home/gabriel/.bun/bin/bun" "/home/gabriel/Workspace/Projects/cukito/node_modules/next/dist/server/lib/start-server.js"
Features: jsc dotenv http_server transpiler_cache(7) tsconfig_paths tsconfig WebSocket
Builtins: "bun:jsc" "bun:main" "node:assert" "node:async_hooks" "node:buffer" "node:child_process" "node:constants" "node:crypto" "node:dns/promises" "node:events" "node:fs" "node:fs/promises" "node:http" "node:https" "node:module" "node:net" "node:os" "node:path" "node:perf_hooks" "node:querystring" "node:stream" "node:stream/web" "node:string_decoder" "node:tls" "node:tty" "node:url" "node:util" "node:util/types" "node:vm" "node:zlib" "node:worker_threads" "ws" "utf-8-validate" "node:v8" "node:diagnostics_channel"
Elapsed: 3474ms | User: 3113ms | Sys: 1331ms
RSS: 3.10GB | Peak: 0.64GB | Commit: 3.10GB | Faults: 418

[cirospaciari]

Looks like this was fixed some time ago. If you're still running into this after Bun v1.3.1 or later, please open a new issue with a reproduction.