Fix line-endings and whitespace issues in bin-folder files #57
Conversation
This file contains 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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Currently, running the bin-files on Linux-OSs fails with
env: node\r: No such file or directorydue to CRLF encodings in most of the bin-files - see the following issue for explanation and background-info: npm/npm#12371I also corrected some whitespace-issues as well, but still recommend to apply some modern formatting guidelines (using prettierjs et.al.) for the whole project, but this would blow the scope of this PR.
After this PR e.g.
./bin/groupreadruns successful on my (Linux-) box again.