chore: remove declarationMap and restrict published files#29
Conversation
Remove declarationMap from tsconfig as declaration maps are not needed. Add files field to both packages to exclude tsconfig.check.json, tsconfig.tsbuildinfo, and src from the published npm package.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (3)
💤 Files with no reviewable changes (1)
WalkthroughThe changes update build and publication configuration for the monorepo. Two package.json files now explicitly specify publishable contents, and the TypeScript configuration disables declaration map generation during compilation. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Summary
declarationMap: truefrom roottsconfig.json— declaration maps are not needed for consumersfilesfield to bothesrouteand@esroute/litpackages to only publishdist/,LICENSE, andREADME.md, excludingtsconfig.check.json,tsconfig.tsbuildinfo, and source filesTest plan
npm run buildand confirm no.d.ts.mapfiles indist/npm pack --dry-runin each package and confirm onlydist/,LICENSE, andREADME.mdare includedSummary by CodeRabbit