QVAC-21220 doc: update npm package homepage metadata#2810
Merged
Conversation
Contributor
Review StatusCurrent Status: ✅ APPROVED |
GustavoA1604
approved these changes
Jun 23, 2026
Contributor
Tier-based Approval Status |
NamelsKing
approved these changes
Jun 24, 2026
Contributor
Author
|
/review |
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.
What problem does this PR solve?
On each npm package's page, the "homepage" field links to the corresponding README on GitHub.
For example: https://www.npmjs.com/package/@qvac/sdk links to https://github.com/tetherto/qvac/tree/main/packages/sdk#readme
Desired behavior:
The npm homepage should always point to the main QVAC website: https://qvac.tether.io
How does it solve it?
Currently, the "homepage" metadata field for all packages in the QVAC monorepo points to their respective README URLs.
This PR performs a bulk edit to update and standardize this specific "homepage" field across all 31 packages published in npm.
Test
The change affects only metadata (the
homepagefield in thepackage.jsonof each package published to npm), with no impact on build or runtime.To ensure no edits broke the JSON syntax (e.g., a missing comma), I locally validated all
packages/*/package.jsonfiles usingJSON.parsewithin a Node script that iterates through each file and fails if parsing is unsuccessful.Result: 32 files parsed successfully, 0 invalid.