Why should I delete source maps after uploading them?

Deleting source maps from your public build folder prevents external parties from easily reconstructing your original source code while still allowing your error tracking service to provide readable stack traces.

Does it work with Sentry and Datadog?

Yes, it includes detailed instructions for uploading maps to Sentry, Datadog, and New Relic using both plugin-based and CLI-based methods.

Which build tools does this skill support?

This skill provides specific configurations for Vite, Webpack (including Next.js and CRA), esbuild, and Rollup/SvelteKit.

How do I verify that my source map setup is actually working?

The skill provides verification commands, such as using the Sentry CLI to list release files and performing a manual error test to confirm the stack trace symbolication.

Source Map Setup & Symbolication

Name: Source Map Setup & Symbolication
Author: nexus-labs-automation

bynexus-labs-automation

Analytics & Monitoring

Configures source maps across build tools and CI/CD pipelines to enable readable production stack traces.

About

The Source Map Setup skill provides comprehensive guidance for transforming minified production errors into readable code references. It automates the configuration of popular build tools like Vite, Webpack, esbuild, and Rollup, ensuring that source maps are generated and uploaded correctly to error tracking services like Sentry or Datadog. By following its security-first patterns, developers can maintain high-quality observability while ensuring original source code remains private and inaccessible to the public web.

Key Features

Step-by-step verification workflows for symbolication
Multi-tool support for Vite, Webpack, esbuild, and Rollup
0 GitHub stars
Security-focused 'upload and delete' implementation patterns
Vendor-specific setup for Sentry, Datadog, and New Relic
CI/CD integration for GitHub Actions and Vercel

Use Cases

Securing production environments by removing source maps after upload
Debugging minified production errors with readable stack traces
Automating source map uploads within CI/CD pipelines

About

Key Features

Step-by-step verification workflows for symbolication
Multi-tool support for Vite, Webpack, esbuild, and Rollup
0 GitHub stars
Security-focused 'upload and delete' implementation patterns
Vendor-specific setup for Sentry, Datadog, and New Relic
CI/CD integration for GitHub Actions and Vercel

Use Cases

Securing production environments by removing source maps after upload
Debugging minified production errors with readable stack traces
Automating source map uploads within CI/CD pipelines