skills.rest
theslashdojo
theslashdojoOFFICIAL
Explore all skills by this author →
GitHub

source-maps

Upload source maps to Sentry via build plugins or sentry-cli.

Updated Apr 10, 2026
Search Tags:#release-management#sentry#upload#ci#source-maps#sourcemaps#debug-ids
One-click install
npx skills add https://github.com/theslashdojo/dojo --skill source-maps
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: source-maps
Source: https://github.com/theslashdojo/dojo/tree/main/nodes/sentry/source-maps
Command: npx skills add https://github.com/theslashdojo/dojo --skill source-maps

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @sentry/cli, and includes scripts (resource) components.

What problem does it solve?

Source maps bridge production stack traces back to the original source code by uploading maps to Sentry, enabling readable error reporting.

Core Features & Use Cases

  • Automates source map uploads to Sentry via build tool plugins (Vite, Webpack, Rollup, esbuild) or via the sentry-cli in CI, ensuring maps are associated with the correct release.
  • Supports release management workflows including injecting Debug IDs, associating deployments, and deleting maps after upload to protect source code.
  • Suitable for web apps and CI pipelines that require reliable, end-to-end source map handling for production debugging.

Quick Start

Configure SENTRY_AUTH_TOKEN, SENTRY_ORG, and SENTRY_PROJECT, ensure your build generates maps, then choose a method (build plugin or CLI) and run the upload workflow.

Frequently Asked Questions about source-maps

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I upload source maps to Sentry for readable production stack traces?▼

To upload source maps to Sentry, you can automate the process using build tool plugins like Vite, Webpack, Rollup, or esbuild, or use sentry-cli within your CI pipelines. This maps production stack traces back to your original source code for readable error reporting.

What environment variables are required to automate Sentry source map uploads in CI?▼

Automating Sentry source map uploads requires the SENTRY_AUTH_TOKEN, SENTRY_ORG, and SENTRY_PROJECT environment variables. You can also optionally define BUILD_DIR and SENTRY_RELEASE to tie the uploaded maps to a specific release.

Can I use Sentry CLI to upload source maps generated by Vite or Webpack?▼

Yes, you can upload source maps using either build tool plugins for Vite, Webpack, Rollup, and esbuild, or directly via the sentry-cli in your CI workflows. Both methods associate your generated maps with the correct Sentry release.

What is the best way to protect my original source code when uploading source maps to Sentry?▼

The best way to protect your source code during Sentry source map uploads is to delete the maps after the upload is complete. This release management workflow ensures maps are associated with your release while keeping source code out of production.

How do Debug IDs work when managing Sentry source map releases?▼

Debug IDs are injected during the Sentry source map upload process to accurately associate minified production code with the original source. This release management technique ensures reliable end-to-end mapping for production debugging.

Related Skills

Explore More Software Engineering Skills→
TheBushidoCollectiveTheBushidoCollective
187

sentry-release-management

Automate Sentry release creation, commit association, and deployment finalization.

Official
Advanced
telum-aitelum-ai
2

sentry-integration

Integrate Sentry error tracking and performance monitoring in React/Next.js applications.

Official
Intermediate
farmountainfarmountain
1

Bundler Expert

Select and configure bundlers like ESBuild, Webpack, Rollup, or Vite for JavaScript projects.

Community
Intermediate
AgentientAgentient
2

full-stack-error-tracking-with-sentry

Integrate Sentry SDKs for end-to-end error tracking across Next.js, Python, and Firebase.

Official
Advanced