sentry-node-sdk

Full Sentry SDK setup for Node.js, Bun, and Deno. Use when asked to "add Sentry to Node.js", "add Sentry to Bun", "add Sentry to Deno", "install @sentry/node", "@sentry/bun", or "@sentry/deno", or configure error monitoring, tracing, logging, profiling, metrics, crons, or AI monitoring for server-side JavaScript/TypeScript runtimes.

224stars27forksUpdated 6/22/2026

Developer Tools #sdk-setup #bun #observability #deno #tracing #sentry #nodejs #error-monitoring

Security Assessment

Critical Risk(15/100)

Detected risks:

Persistence([references/crons.md] crontab, [references/crons.md] Crontab)

Secret Exposure([SKILL.md] TOKEN=)

Sensitive File Access([references/profiling.md] .env, [references/ai-monitoring.md] .env, [references/error-monitoring.md] .env)

Security Score15/100

About sentry-node-sdk

The Sentry Node.js/Bun/Deno SDK skill is an opinionated setup wizard that automates the complete integration of Sentry error monitoring and observability into server-side JavaScript and TypeScript applications. It intelligently detects your project's runtime environment (Node.js, Bun, or Deno), module system (ESM or CommonJS), and framework (Express, Fastify, Koa, Hapi, etc.), then guides you through the proper Sentry configuration tailored to your specific stack.

This skill provides comprehensive observability features including error tracking, distributed tracing, performance monitoring, profiling, custom metrics, cron job monitoring, logging integration, and AI/LLM monitoring. It handles the complexity of different initialization patterns across runtimes—from Node.js preload hooks (--import) to Bun's --preload flag and Deno's npm specifier imports. The wizard automatically detects existing Sentry installations, OpenTelemetry integrations, logging libraries, scheduling tools, and AI frameworks to ensure seamless integration without conflicts.

Target users include backend developers building APIs, microservices, serverless functions, or full-stack applications who need production-grade error monitoring and performance insights. Whether you're starting a new project or adding observability to an existing codebase, this skill eliminates manual configuration errors and ensures best practices are followed across Node.js, Bun, and Deno environments. It's particularly valuable for teams managing multiple services across different runtimes or migrating between JavaScript runtime environments.

FAQ

Which JavaScript runtimes does this skill support?

This skill supports Node.js, Bun, and Deno server-side runtimes. It automatically detects which runtime you're using and applies the appropriate Sentry SDK (@sentry/node, @sentry/bun, or @sentry/deno) with runtime-specific initialization patterns.

Does this work with NestJS or Next.js frameworks?

No, this skill is for general Node.js/Bun/Deno backend applications. For NestJS, use the sentry-nestjs-sdk skill which provides NestJS-native decorators and filters. For Next.js, use the sentry-nextjs-sdk skill which handles the browser, server, and edge runtime architecture.

What monitoring features are included beyond error tracking?

The skill configures error monitoring, distributed tracing, performance profiling, custom metrics, cron job monitoring, logging integration (Winston, Pino, Bunyan), and AI/LLM monitoring for frameworks like OpenAI, Anthropic, and LangChain. It also detects and integrates with existing OpenTelemetry instrumentation.

How does it handle ESM vs CommonJS module systems?

The skill automatically detects your module system by examining package.json and file extensions. For ESM, it uses --import flags and .mjs instrument files. For CommonJS, it uses require() patterns and .cjs/.js instrument files. This ensures the correct initialization approach for your project.

Can it detect existing Sentry installations?

Yes, the skill scans package.json, deno.json, and existing instrument files to detect prior Sentry setups. It will identify conflicts, suggest upgrades, and avoid duplicate configurations to ensure a clean integration.