Michael H

@efogdev can you try my fix (in canary at moment) and see if it improves the debugger for you. ```zig bun upgrade --canary ```

No, on windows it was fine for me, and I haven't tried a Linux browser (I did try it as running bun tho) I think there is a chance one...

Actually I do remember seeing it "not connect" sometimes, but that was always fixable by typing in the console input. I don't know why that's needed or the other issue...

>@pols63 There is not for Windows in that link, right? Bun didn't have windows back then in 1.0 (but support was added in 1.1), so you can use any recent...

```ts const x = Symbol("test"); console.log(x); ``` with breakpoints: * All exceptions * Assertion failures seems to give this issue `symbol` issue

i just fixed!

Can you clarify what the issue is. I see that you are running `bun update --latest` in many places, but I'mnot sure what the output is and what you were...

It seems like the `proxy` package's test doesn't work well on bun either: https://github.com/TooTallNate/proxy-agents/blob/main/packages/proxy/test/test.ts ```py bun test v1.1.38 (bf2f153f) proxy-repo.test.ts: ✓ proxy > authentication > should invoke the `server.authenticate()` function...

I can reproduce this issue as well, but when I upgraded to the canary version, it seemed to work again. Does upgrading with: ```shell bun upgrade --canary ``` resolve the...

Like [bunx and --bun](https://bun.com/docs/cli/bunx#shebangs), that is intended. Basically anything before script name is the `bun run` specific stuff and things after is what will be sent to your process/script instead...