Get Sentry-like error reporting working

[Jarred-Sumner]

https://nodejs.org/api/process.html#event-uncaughtexceptionmonitor

• process.on("unhandledRejection", cb)
• process.on("unhandledException", cb)
• process.on("uncaughtExceptionMonitor", cb)
• process.setUncaughtExceptionCaptureCallback(cb)

This lets Sentry get error reporting working.

Ideally, the fix would go here:

bun/src/bun.js/javascript.zig

Lines 629 to 640 in 7ce7f08

	pub const UnhandledRejectionScope = struct {
	ctx: ?*anyopaque = null,
	onUnhandledRejection: *const OnUnhandledRejection = undefined,
	count: usize = 0,
	pub fn apply(this: *UnhandledRejectionScope, vm: *JSC.VirtualMachine) void {
	vm.onUnhandledRejection = this.onUnhandledRejection;
	vm.onUnhandledRejectionCtx = this.ctx;
	vm.unhandled_error_counter = this.count;
	}
	};

We would add an unhandled rejection scope for either rejections or exceptions and have some way to distinguish between the two. This one would call into JS potentially for multiple handlers. The part that gets a little tricky is in unit tests where we rely on this behavior for expect().toThrow()

cc @dcramer

[HazAT]

We will release the Sentry SDK this week - Most things work (manually) once this lands we'll shoot out an update supporting it. Few users already asked for Sentry Bun SDK 😅

[AbhiPrasad]

We just shipped https://www.npmjs.com/package/@sentry/bun as part of https://github.com/getsentry/sentry-javascript/releases/tag/7.70.0.

bun add @sentry/bun

[HazAT]

I don't want to spam here 😅 but with version 7.71.0 of the Sentry Bun SDK we wrap Bun.serve automatically getsentry/sentry-javascript#9080 capturing Errors and Transactions that happen during requests.

[colindotfun]

#7472 still seems to be an issue with:

- `@sentry/bun version 7.93.0`
- `bun version 1.0.20`

[GingerAdonis]

I'm aware that the team has lots of things to work on, but I'd like to say that this is likely a blocker for many to use Bun in production.

[ohbob]

^^ please fix

[thecrabcode]

I agree with @GingerAdonis, this is very important for many devs. Do you guys have any estimates on when this could potentially be fixed?