Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThis pull request fixes a critical CLI parsing issue in the router-cli package introduced in version 1.166.9. The fix modifies the CLI entrypoint to correctly pass command-line arguments to yargs by using Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
📝 Coding Plan
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 |
|
View your CI Pipeline Execution ↗ for commit aca1e84
☁️ Nx Cloud last updated this comment at |
🚀 Changeset Version Preview1 package(s) bumped directly, 0 bumped as dependents. 🟩 Patch bumps
|
Bundle Size Benchmarks
Trend sparkline is historical gzip bytes ending with this PR measurement; lower is better. |
Merging this PR will not alter performance
Comparing Footnotes
|
The vite-config upgrade in #6923 changed
import * as yargstoimport yargs from 'yargs'and switched from the yargs singleton API (yargs.scriptName(...)) to the factory API (yargs().scriptName(...)).However, calling
yargs()without arguments creates an instance with no args to parse, so all commands (generate, watch, --help) silently did nothing.Fix: pass
hideBin(process.argv)so the new instance receives CLI args, as suggested in the docs:https://yargs.js.org/docs/#api-reference
Fixes #6968
Summary by CodeRabbit