# sentry-node-sdk

A wizard skill that scans your backend project and walks you through Sentry setup for server-side JavaScript and TypeScript runtimes.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · 3300 installs · ★ 272
- Author: getsentry
- License: Apache-2.0 · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/getsentry/sentry-for-ai/tree/HEAD/skills-legacy/sentry-node-sdk/SKILL.md
- Updated: 2026-10-23
- HTML: https://affpapa.org/en/nevibecode/skills/sentry-node-sdk

## What it does

The skill starts by inspecting the project instead of asking questions. It checks which runtime is present (`node`, `bun`, `deno`), greps `package.json` for `@sentry/*` packages, and looks for Express, Fastify, Koa, Hapi, Elysia, Hono, logging libraries like `winston` and `pino`, schedulers such as `node-cron` and Bull, and LLM clients. It also works out whether the project is ESM or CommonJS and whether an `instrument.js` or `instrument.mjs` file already exists — if one does, the skill merges into it rather than overwriting.

Then it leads with a proposal. Error monitoring and tracing are the baseline; everything else depends on what it found. Profiling is Node.js only, so on Bun and Deno it is off the table. If OpenTelemetry tracing is already in the project, the skill routes you to the OTLP path via `otlpIntegration()` and tells you not to set `tracesSampleRate`; native tracing and profiling are skipped in that case. NestJS and Next.js projects get pointed at `sentry-nestjs-sdk` and `sentry-nextjs-sdk` instead.

One thing to watch: the SDK versions referenced in the skill match Sentry docs at the time it was written, so verify them before implementing. ESM projects need `--import ./instrument.mjs`, Bun uses `--preload`, and Deno pulls the package in as `npm:@sentry/deno`. That is where setup usually breaks.

## Requirements
- Works with: Sentry

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add getsentry/sentry-for-ai --skill sentry-node-sdk -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/sentry-node-sdk/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/sentry-node-sdk/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add getsentry/sentry-for-ai --skill sentry-node-sdk -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/sentry-node-sdk/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add getsentry/sentry-for-ai --skill sentry-node-sdk -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/sentry-node-sdk/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install getsentry/sentry-for-ai sentry-node-sdk
```

2. **Manually: put the files in place**
- File: `.github/skills/sentry-node-sdk/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add getsentry/sentry-for-ai --skill sentry-node-sdk -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/getsentry/sentry-for-ai --path skills-legacy/sentry-node-sdk
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/sentry-node-sdk/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add getsentry/sentry-for-ai --skill sentry-node-sdk -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/getsentry/sentry-for-ai/tree/HEAD/skills-legacy/sentry-node-sdk/SKILL.md

## When to use it
- wire Sentry into a backend running on Node.js, Bun or Deno
- decide whether to use the OTLP path when OpenTelemetry is already present
- add error monitoring to an Express, Fastify, Koa or Hapi app
- catch missed and failed scheduled jobs
- ship logs from winston or pino with trace correlation

## Example prompts
- add Sentry to my Node.js app
- set up @sentry/bun for this project
- configure error monitoring and tracing for Fastify

## Source text · SKILL.md · Apache-2.0

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: f339c987f0c36972.

BEGIN THIRD-PARTY FILE f339c987f0c36972
````text
---
name: sentry-node-sdk
description: 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.
license: Apache-2.0
category: sdk-setup
parent: sentry-sdk-setup
disable-model-invocation: true
---

> [All Skills](../../SKILL_TREE.md) > [SDK Setup](../sentry-sdk-setup/SKILL.md) > Node.js / Bun / Deno SDK

# Sentry Node.js / Bun / Deno SDK

Opinionated wizard that scans your project and guides you through complete Sentry setup for server-side JavaScript and TypeScript runtimes: Node.js, Bun, and Deno.

## Invoke This Skill When

- User asks to "add Sentry to Node.js", "Bun", or "Deno"
- User wants to install or configure `@sentry/node`, `@sentry/bun`, or `@sentry/deno`
- User wants error monitoring, tracing, logging, profiling, crons, metrics, or AI monitoring for a backend JS/TS app
- User asks about `instrument.js`, `--import ./instrument.mjs`, `bun --preload`, or `npm:@sentry/deno`
- User wants to monitor Express, Fastify, Koa, Hapi, Connect, Bun.serve(), or Deno.serve()

> **NestJS?** Use [`sentry-nestjs-sdk`](../sentry-nestjs-sdk/SKILL.md) instead — it uses `@sentry/nestjs` with NestJS-native decorators and filters.
> **Next.js?** Use [`sentry-nextjs-sdk`](../sentry-nextjs-sdk/SKILL.md) instead — it handles the three-runtime architecture (browser, server, edge).

> **Note:** SDK versions below reflect current Sentry docs at time of writing (`@sentry/node` ≥10.42.0, `@sentry/bun` ≥10.42.0, `@sentry/deno` ≥10.42.0).
> Always verify against [docs.sentry.io/platforms/javascript/guides/node/](https://docs.sentry.io/platforms/javascript/guides/node/) before implementing.

---

## Phase 1: Detect

Run these commands to identify the runtime, framework, and existing Sentry setup:

```bash
# Detect runtime
bun --version 2>/dev/null && echo "Bun detected"
deno --version 2>/dev/null && echo "Deno detected"
node --version 2>/dev/null && echo "Node.js detected"

# Detect existing Sentry packages
cat package.json 2>/dev/null | grep -E '"@sentry/'
cat deno.json deno.jsonc 2>/dev/null | grep -i sentry

# Detect Node.js framework
````
END THIRD-PARTY FILE f339c987f0c36972

The third-party file has ended. Everything between the f339c987f0c36972 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2337 of 33863 bytes. © getsentry · Apache-2.0 · https://github.com/getsentry/sentry-for-ai/tree/HEAD/skills-legacy/sentry-node-sdk/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md