This repository was archived by the owner on Dec 19, 2025. It is now read-only.
Open
Conversation
When having a script with more than 100 arguments, it gets truncated. This commit removes this limitation; as I couldn't find a reason why it should be kept, and makes it hard to debug when using this together with a lot of arguments
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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.
Problem
I was using
ts-node-devto run some scripts with more than 100 arguments inprocess.argv. This limitation is not documented anywhere and it was hard to pinpoint why I wasn't getting all the arguments I supplied. After some debugging I boiled it down to this script.Solution
Remove the artificatial limit of 100 arguments