Source maps available
Why it matters
When a consumer encounters a bug that originates inside your package, their stack trace shows transpiled or minified output — line numbers and variable names from dist/index.cjs line 1 that bear no resemblance to the original source. Without source maps, debugging requires manually cloning your repo, matching the version, and mapping the call site. ISO 25010 analysability degrades directly: the time-to-understand a stack trace goes from seconds to minutes.
Severity rationale
Low because source maps affect debugging ergonomics only — the absence does not cause runtime failures, and determined consumers can still diagnose issues by reading the compiled output.
Remediation
Enable source map generation in your build tool and include the .map files in the published package.
// tsup.config.ts:
import { defineConfig } from 'tsup'
export default defineConfig({ sourcemap: true })
// tsconfig.json — for declaration maps:
{
"compilerOptions": { "declarationMap": true }
}
Verify that .js.map files appear in dist/ after building and that your files field in package.json includes the dist directory (so maps are published). At least one .map file must be present in the published package for this check to pass.
DetectionPro
The detection method for this pattern is part of AuditBuffet Pro.
The full method (what to look for, pass and fail conditions, and how results get reported) ships inside the SDK / Package Quality Audit. The pattern definition, severity rationale, and remediation remain openly licensed under CC-BY-4.0.
External references
- iso-25010:2011 · maintainability.analysability — Analysability — source maps allow consumers to trace errors to original source
Taxons
History
- 2026-04-18·v1.0.0·Initial import from sdk-package-quality·automated