clover caruso

should we consider https://github.com/oven-sh/bun/issues/4464

there are some existing breaking changes behind compile time feature flags. these can be inspected by doing a code search for `breaking_changes_1_2` - websocket server: `ws.subscribe()` function will require a...

logging this here - make `Bun.build` a rejected promise on failure. people continue to run into this footgun that a failing build returns an object with `success: false`, especially when...

- Bun.build will add the condition "development" when NODE_ENV is not development. This allows `esm-env` (used by svelte) to use the correct variable. Bake already does this.

minimum reproduction: ```ts import * as vm from 'node:vm'; class A { globalThis = this; constructor() { vm.createContext(this); new vm.Script('this.eval = globalThis.eval').runInContext(this); } } console.log(new A()); expect(new A().eval).toBe(eval); ```

additionally, `--compile` and `--target=browser` are mutually exclusive and should be an error instead of silently discarding `--target`

the second crash (the one in bunx) is a duplicate of raiseIgnoringPanicHandler issue #12169. that is simply just forwarding the inner crash into `bunx` for no reason. we will focus...

an interesting, but rare, use case for `@returnAddress` at comptime is in `std.debug.panicExtra` / panic handler. At runtime, it is given an address to dump the stack for, but at...

If you re-run this on the latest version of bun, it should print what file it was parsing when it crashed. This could help narrow the bug down if it...

thanks for this report. i spot two bugs: 1. outside of `--compile`, we see a remapped stack trace. --compile with sourcemaps is bugging up.  2. the stated error: eV...