Bun inspect override prefix not working.

[JaydenL33]

What version of Bun is running?

1.0.2+37edd5a6e389265738e89265bcbdf2999cb81a49

What platform is your computer?

Linux 5.10.16.3-microsoft-standard-WSL2 x86_64 x86_64

What steps can reproduce the bug?

Running bun --inspect=localhost:6499/forcingPrefix server.ts is not forcing the URL prefix to come through in the debug URL.

What is the expected behavior?

--------------------- Bun Inspector ---------------------
Listening:
ws://localhost:6499/forcingPrefix

What do you see instead?

--------------------- Bun Inspector ---------------------
Listening:
ws://localhost:6499/gzm88zwftcg

Additional information

Happy to help where i can to fix this issue.

[natefabian18]

Any updates on this issue. It is a large blocking point for me working on some projects with Bun.

[xlc]

With this random suffix, I have to copy the url every thing time and that completely kills productivity.
And it is more fun with --watch.

We need a way to not have this random suffix, and also ensure it remains the same in watch mode.

And paste the new inspect url on the same browser (Chrome) window doesn't update it. I need to open a new window.

[abelcha]

I found a workaround, you just need specify the ws protocol in the url

ws:// localhost:6499/forcingPrefix --> works
localhost:6499/forcingPrefix --> dont works

bun run --inspect=ws://localhost:6499/forcingPrefix src/generate-dataset.ts
--------------------- Bun Inspector ---------------------
Listening:
  ws://localhost:6499/forcingPrefix
Inspect in browser:
  https://debug.bun.sh/#localhost:6499/forcingPrefix
--------------------- Bun Inspector ---------------------
HELLO RUNNINGM AIN YYY dddsss999

[june07]

With this random suffix, I have to copy the url every thing time and that completely kills productivity. And it is more fun with --watch.

We need a way to not have this random suffix, and also ensure it remains the same in watch mode.

And paste the new inspect url on the same browser (Chrome) window doesn't update it. I need to open a new window.

An age old problem as similarly experienced with Node.js early on. While there is a good reason for the "random" path/id to change each time (security), it can break ones workflow and be a real pain.

I submitted this change, which is meant to allow for tooling that can serve as a fix for this exact issue, among other niceties.

#13219 (comment)