Run the link-check bin directly, not via npx#480
Merged
chalin merged 1 commit intoJul 22, 2026
Conversation
- Drops `npx` from the `_check:links` script: the bin comes from the git-only `link-cache` devDependency, so it is never fetchable from the npm registry by that name. - With `npx`, a stale or missing `node_modules` silently falls back to the public registry, executing whatever package holds the name there. The bare bin name resolves via `node_modules/.bin` (on the PATH under `npm run`) and fails loudly (exit 127, no network) when the install is missing.
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.
npxfrom the_check:linksscript:npm runalready putsnode_modules/.binon thePATH, so the bin provided by thelink-cachedevDependency resolves directly.npx BINsilently falls back to the public npm registry whennode_modulesis stale or missing, executing whatever package claims that name there; a bare bin name instead fails loudly (exit 127) with zero registry traffic.node_modules, it exits 127 with no network access.