chore: verify npm package content before publishing#999
Merged
Conversation
OrKoN
force-pushed
the
orkon/verify-npm
branch
from
61e5952 to
7a4d290
Compare
Contributor
|
What about checking if |
Collaborator
Author
I do not think it is worth it for multiple reasons. But happy to review a PR with that :) |
OrKoN
force-pushed
the
orkon/verify-npm
branch
from
7a4d290 to
59e7e24
Compare
OrKoN
force-pushed
the
orkon/verify-npm
branch
from
59e7e24 to
e2b3ad3
Compare
OrKoN
force-pushed
the
orkon/verify-npm
branch
from
e2b3ad3 to
5dab9aa
Compare
wolfib
pushed a commit
to wolfib/chrome-devtools-mcp
that referenced
this pull request
Mar 10, 2026
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.
Refs: #996 #995