chore: point homepage at kkdev92.dev - #38
Merged
Merged
Conversation
`homepage` pointed at the GitHub readme, which `repository` already covers. The site is the project's own front door, and this matches health-data-dotnet, where `PackageProjectUrl` is already https://kkdev92.dev/. npm renders this as the package page's Homepage link; `repository` and `bugs` are separate fields and unchanged, so the repo and the issue tracker are still linked from there. `format:check` and `verify:package` both pass, and the packed tarball carries the new value. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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.
homepagewashttps://github.com/kkdev92/vscode-ext-kit#readme— whichrepositoryalready covers. This points it at the project's own site, matchinghealth-data-dotnet, where<PackageProjectUrl>is alreadyhttps://kkdev92.dev/.One line.
homepageappears nowhere else in the tracked tree — no test, script or document reads it, andscripts/verify-package.mjsasserts no metadata fields.Nothing is lost from the npm page:
repositoryandbugsare separate fields and unchanged, so the repository and issue links stay.Verified:
format:checkandverify:packageboth exit 0, andnpm packcarrieshomepage: https://kkdev92.dev/withrepositoryandbugsintact.The GitHub repository homepage field is deliberately left pointing at the npm package page — same split as health-data-dotnet, where the GitHub field points at NuGet and the package metadata points at the site.
🤖 Generated with Claude Code