Bun runtime setup being added for Sentry error tracking
Developers using Bun can now properly configure Sentry error tracking in Trigger.dev projects, with documentation explaining how to avoid a runtime error caused by esbuild bundling @sentry/node's CJS entry during local development.
Developers using the Bun runtime with Sentry error tracking hit a runtime error in local development. The issue stems from esbuild's bundling of @sentry/node's CJS entry, which causes conflicts when Bun tries to resolve the module.
The documentation now includes a "Bun runtime" section with a working configuration. Developers add an extension that marks @sentry/node as external during development only, letting Bun resolve it directly from node_modules. For deployment, the module is bundled normally.
This fix appears in the Sentry error tracking guide under docs/guides/examples/, helping Bun users get local error tracking working without manually workarounds.