fix: incorrect argument indexing in CLI input #641
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why?
The script was incorrectly parsing CLI arguments by slicing
process.argvfrom index 1 instead of 2. This caused the first user-provided argument to be shifted, leading to confusion and potential bugs.How?
Changed
process.argv.slice(1)toprocess.argv.slice(2). Now,args[0]correctly refers to the first argument — the filepath. Logic and comments remain untouched ✅Tickets?
No formal ticket — just cleaning up a subtle issue before it causes trouble.
Contribution checklist?
buildcommand runs locallySecurity checklist?
References?
None needed — standard Node.js CLI behavior
Preview?
N/A