Conversation
This branch has not been deployed
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
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.
Two things.
ppn --versionanswered nothing before, and a bare number is misleading in a checkout, where package.json holds the placeholder the release rewrites at publish. And the README showed one fork example, so the no-sudo half of forking was invisible.ppn versionreports the version plus how the copy was installed: a dist reads its release manifest, an npm install the stamped package version, a checkout falls back to git HEAD.--jsonfor consumers.ppn --version/-Vprint the bare number.ppn biteon its own, fork resume and--clean,--pin-products, remote upgrades, the duplicate security block removed.