Repository navigation
fix: ignore NPM details of private packages - #56
Merged
Merged
Conversation
bjohansebas
approved these changes
Aug 9, 2026
Contributor
Author
|
CI won't pass without #54 |
Packages with `"private": true` in package.json by definition cannot be published on NPM.
krzysdz
force-pushed
the
skip-private-packages
branch
from
September 26, 2026 20:12
54275fb to
92080ba
Compare
my mistake from pkgjs#55
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
2 participants
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.
Packages with
"private": truein package.json by definition cannot be published on NPM. This reduces the number of 404s in logs and hides badges of NPM packages that don't exist or are owned by somebody else.The link on stars badge was changed to point to GitHub repo, because that's where stars are and repos without package.json had this link as
https://npmjs.org/package/null.Closes #53