sentry-local-dev-loop

# Sentry Local Dev Loop ## Overview Configure Sentry for local development with environment-aware DSN routing, debug-mode verbosity, full-capture sample rates, `beforeSend` inspection, Sentry Spotlight for offline event viewing, and `sentry-cli` source map verification. All configuration uses environment variables so nothing leaks into commits. ## Prerequisites - `@sentry/node` v8+ installed (TypeScript/Node) or `sentry-sdk` v2+ installed (Python) - Separate Sentry project created for development (different DSN from production) - `.env` file with `SENTRY_DSN_DEV` and `NODE_ENV=development` - Network access to `*.ingest.sentry.io` (or use Spotlight for fully offline work) ## Instructions ### Step 1 -- Environment-Aware Configuration Create an initialization file that routes events to the correct Sentry project based on environment, enables debug logging in dev, and captures 100% of traces locally: ```typescript // instrument.mjs — import via: node --import ./instrument.mjs app.mjs import * as Sentry from '@sentry/node'; const env = process.env.NODE_ENV || 'development'; const isDev = env !== 'production'; Sentry.init({ // Route to dev project locally, prod project in production dsn: isDev ? process.env.SENTRY_DSN_DEV : process.env.SENTRY_DSN, environment: env, release: isDev ? 'dev-local' : process.env.SENTRY_RELEASE, // Full capture in dev — you need every event for debugging tracesSampleRate: isDev ? 1.0 : 0.1, sampleRate: isDev ? 1.0 : 1.0,...