fix: include CLI binaries in package build - #522
Conversation
Signed-off-by: Emre K <110906681+kocaemre@users.noreply.github.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Team Run ID: 📒 Files selected for processing (2)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. WalkthroughThe tsup configuration now builds the main bundle and two CLI binaries. A new test verifies that the package ChangesCLI binary packaging
Estimated code review effort: 2 (Simple) | ~10 minutes Merge Risk: ⚪ Minimal · up to The package will now build and ship its two already-declared CLI commands, with a regression test keeping package metadata and build entries aligned. No actionable merge-blocking risk remains after normal checks and review. Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
Full details: Linked Issues checkExplanation The PR addresses issue Full details: Docstring CoverageExplanation No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 2 files. ✨ 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
Fixes #500.
Test plan
Note: I also tried the repository-wide
npm run lint; it currently reports pre-existing generated/stale formatting errors outside this change (for exampledist/index.d.ts,lib/DateTimeUtils.ts, andlib/utils/result_formatter.test.ts). The touched-file lint command above passes.Summary by CodeRabbit
New Features
Bug Fixes
Tests