Fix stale pre-rename npm links and outdated publish status across READMEs - #34
Merged
Conversation
…DMEs Every package README except the root and CLI's own still linked to npmjs.com/package/vayo - the old, unscoped CLI name that npm actually rejected as a first-publish typosquat, never scoped/@vayo-hq/cli. Also fixed db-mongo's README claiming its adapter is never called directly, which contradicts the wiring snippet every other doc shows, and updated the root README's "Using Vayo" section, which still described a build-your-own-tarball workflow from before any package was actually published. Every install example now explicit about the @beta tag rather than relying on latest, since latest only moves on an explicit re-tag during this prerelease period.
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.
Summary
vayonpm package name (npm rejected it on first publish as a typosquat) — now point to the real@vayo-hq/cli.@vayo-hq/db-mongo's README claiming its adapter is "never called directly," which contradicted the wiring snippet every other doc shows andvayo init's own printed next steps.npm install ...@betacommand.@betatag rather than relying onlatest(which only moves on an explicit re-tag during this prerelease period — the root cause of a real bug found this session wherelatestpointed at a broken version for hours after the fix was published underbeta).Test plan
pnpm lintpassesnpmjs.com/package/vayolinks anywhere in the repo (excluding CHANGELOGs, which are historical record)