Skip to content

Add missing npm package metadata - #1148

Open
Turbo87 wants to merge 1 commit into
pierrecomputer:mainfrom
Turbo87:package-metadata
Open

Turbo87 wants to merge 1 commit into
pierrecomputer:mainfrom
Turbo87:package-metadata

Conversation

@Turbo87

@Turbo87 Turbo87 commented Sep 21, 2026

Copy link
Copy Markdown

Description

The publishable packages now all declare repository, homepage, and bugs metadata so npm and other package tools can link to their source code, homepages, and issue tracker. Each repository entry also identifies the package subdirectory within the monorepo now. This mirrors what the @pierre/theme package already contains.

Motivation & Context

The renovatebot update PRs that I get for the pierre packages don't contain any repository links, and also no changelog. Adding this metadata should hopefully fix that issue.

Type of changes

  • Bug fix (non-breaking change which fixes an issue)
  • Refactoring (non-breaking change)
  • New feature (non-breaking change which adds functionality). You must have
    first discussed with the dev team and they should be aware that this PR is
    being opened
  • Breaking change (fix or feature that would change existing functionality).
    You must have first discussed with the dev team and they should be aware
    that this PR is being opened
  • Documentation update

Checklist

  • I have read the
    contributing guidelines
  • My code follows the code style of the project (moon run root:lint)
  • My code is formatted properly (moon run root:format)
  • I have updated the documentation accordingly (if applicable)
  • I have added tests to cover my changes (if applicable)
  • All new and existing tests pass (moonx diffs:test)

How was AI used in generating this PR

I used Codex for a quick search if this omission was intentional and then used it to add the missing metadata keys.

Related issues

@vercel

vercel Bot commented Sep 21, 2026

Copy link
Copy Markdown

@Turbo87 is attempting to deploy a commit to the Pierre Computer Company Team on Vercel.

A member of the Team first needs to authorize it.

The publishable packages now declare `repository`, `homepage`, and `bugs`
metadata so npm and other package tools can link to their source code,
homepages, and issue tracker. Each repository entry also identifies the package
subdirectory within the monorepo now.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant