Skip to content

Set up package.json repository field for GitHub Packages sidebar on npm publish #35

@adiled

Description

@adiled

GitHub auto-links published npm packages back to the repo when package.json has a correct repository field. The result is a "Packages" entry in the repo's right sidebar showing npm version, download counts, and a link to the npm page. Free advertising and a credibility signal at the moment a launch lands.

This issue is to make sure the linkage works the moment clwnd hits npm publish.

Action

  • Confirm package.json has a repository field of the form:
    "repository": {
      "type": "git",
      "url": "git+https://github.com/adiled/clwnd.git"
    }
  • If missing or wrong, add or correct it.
  • After the first npm publish, verify the "Packages" sidebar appears on the repo's main page within a few minutes. If it doesn't show, recheck the repository URL and republish a patch.

Context
Tracked in the distribution playbook at adiled/distribution. Companion to the npm publish step in the T2 launch checklist.

~ distribution team

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions