190n
190n
Could you reopen this issue? Or should I open a new one? The reproducer script still shows the same buggy behavior for me in v0.1.68.
#14501 includes this change and has been merged
This assertion failure in test-worker-message-port-transfer-terminate is interesting: https://buildkite.com/bun/bun/builds/18199#01974255-d25e-4706-8891-290500bfd29b/2013-2014 Trying to repro
This is happening because some object has a `[util.inspect.custom]` function which throws. In Bun, passing such an object to `util.inspect` will throw the error (which is how it works in...
Here's a smaller reproduction: ```ts // root.ts const { getValue } = await import('./module'); // with static instead of dynamic import it works // import { getValue } from './module';...
> Should bind set unrefOnBind to false? Probably, to be safe, although I don't think you can call `bind` twice without errors.
NVM I broke the bigint tests. Will fix
> This proposal competes with #15764. As the author of that proposal, I'd prefer this solution. It goes further than I did to address the same issue I was trying...
Why should Bun block these ports? What if you want to connect to a service that happens to be running on one of them? It makes sense that the fetch()...
> a library developed with Bun will run headfirst into issues precisely because Bun's fetch allows things others don't This is the strongest argument I've seen, but I still think...