The Journey of Building the Sentry Nuxt SDK
summary
Sentry ships a new Nuxt module that implements client, server and build-time configs separately, targets Nuxt 3/Nitro/H3, and integrates source‑map upload and runtime init via a generated plugin. The main engineering problem is OpenTelemetry’s lack of CJS-style monkey‑patching for ESM, solved with a loader‑hook approach and a rollup plugin that rewrites output to call init before a dynamic import, enabling backend traces. SDK supports ~30 JS SDKs and is currently beta.
AI-written summary · about
chapters (12)
- 0:00Building Sentry Nuxt SDK
- 1:05Sentry’s JS SDK ecosystem
- 2:31Requirements for Nuxt SDK
- 3:57Server and client settings
- 5:20Client-side monitoring in Nuxt
- 6:45Server-side monitoring challenges
- 7:27OpenTelemetry and monkey patching
- 9:14JavaScript module loading
- 10:41ESM module loading limits
- 12:31Solving ESM limits with loader hooks
- 13:58Improving developer experience with dynamic imports
- 15:04SDK current state and next steps
related talks
39mUnJS: Nuxt 3 behind the scenes
22mDeep dive into Nuxt.js
18mNuxt.js - Just Vue and a bit of magic?
35mFull stack development with Nuxt 3 and Nitro
27mNuxt 3 – More Than Vue 3 on Steroids
30mPerformance-Minded Development with Nuxt 3
21mState of Nuxt 2023
41mBuilding for the Edge with Nuxt 3 (live coding)