build: stop emitting source maps and declaration maps - #13
Conversation
Publishing policy is compiled output only. The npm tarball carried a .js.map and .d.ts.map next to every module; the tsconfig now emits neither.
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Essentials Run ID: 📒 Files selected for processing (1)
Included review availability: 0 reviews are currently available. Your included PR review attempts over the past 7 days set your current allowance at 4 reviews per hour. 📝 WalkthroughWalkthroughThe TypeScript configuration disables declaration map and source map generation. ChangesBuild Output Configuration
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~2 minutes Change: Bug fix Merge Risk: ⚪ Minimal · up to The change removes source-map artifacts from the package without altering exported declarations, and is ready to merge. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
A rabbit checks the compiler's chart Comment |
Publishing policy is compiled output only. The npm tarball carried a
.js.mapand.d.ts.mapnext to every module (58 map files in 3.10.0); the tsconfig now emits neither.Verified:
npm run buildOK,npm pack --dry-runhas 0.mapfiles (unpacked size 174 kB → 95 kB),vitest runpasses.Note: this repo is public, so the code itself is available regardless; this only removes the redundant maps from the package.
Summary by CodeRabbit