Repository navigation
fix: node --check only checked the first file, check every file - #1164
Merged
Merged
Conversation
node --check takes one file, so the shell-expanded globs in npm run check silently skipped every file after the first. The check script now walks the tree and runs node --check on each .js, .mjs and .cjs file, failing if any fails.
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
node --check takes one file, so the shell-expanded globs in npm run check skipped everything after the first file in each glob (a two-file repro with a syntax error in the second exits 0). npm run check now runs node --check on every .js, .mjs and .cjs file (450 files currently, all pass). Adds tests for the script.