Skip to content

chore: describe the installer and the examples for npm - #257

Merged
fernandomg merged 4 commits into
mainfrom
chore/npm-metadata-installer-examples
Oct 30, 2026
Merged

fernandomg merged 4 commits into
mainfrom
chore/npm-metadata-installer-examples

Conversation

@fernandomg

@fernandomg fernandomg commented Oct 30, 2026 •

Copy link
Copy Markdown
Member

Summary

Closes #256

create-canton-dappbooster and both example packages shipped 0.7.0 with no keywords, homepage, bugs or author on their npm pages, which the three libraries have. This fills them in and adds a test so a published package can't miss them again. The fields reach npm with the next publish.

Changes

  • The installer and both examples declare keywords, homepage, bugs and author;
  • pnpm test fails when a published package misses a field its npm page shows;
  • CLAUDE.md states the rule.

Acceptance criteria

None.

Test plan

Automated tests

  1. node --test scripts/manifests.test.mjs passes; on main's manifests it fails and lists the twelve missing fields.

Manual verification

  1. pnpm -C canton-create pkg get keywords homepage bugs author shows the four fields.

Breaking changes

None.

Checklist

  • Self-reviewed my own diff
  • Tests added or updated
  • Docs updated (if applicable)
  • No unrelated changes bundled in

Screenshots

None.

- keywords, homepage, bugs and author on create-canton-dappbooster and both examples
- canton, dapp, dappbooster and bootnode on all three; bugs and author match the libraries
…d package

- manifests.test.mjs fails pnpm test when a published package misses one of them
- CLAUDE.md states the rule beside the repository one
Copilot AI balanced review requested due to automatic review settings October 30, 2026 10:43
@vercel

vercel Bot commented Oct 30, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
components.canton-dappbooster Ready Ready Preview Oct 30, 2026 1:47pm UTC
demo.canton-dappbooster Ready Ready Preview Oct 30, 2026 1:47pm UTC

Request Review

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 Approval recommended

The review surfaced no objective defects, with the metadata additions, the regression test, and the documentation all found consistent and leaving nothing outstanding to address.

No open issues 🎉

What changed in this PR

This PR fills in the npm-page metadata (keywords, homepage, bugs, author) for the three packages that were missing it — the create-canton-dappbooster installer and the two example dApps — bringing them in line with the three published libraries, which already carried these fields. It also adds a regression test so a future published package can't ship without them, and documents the rule in the monorepo's canonical CLAUDE.md. The fields take effect on the next publish.

Changes:

  • Add keywords, homepage, bugs, and author to canton-create, example-dapps/amulet-vesting, and example-dapps/token-vesting.
  • Add a scripts/manifests.test.mjs case that fails pnpm test (and the release workflow) if any non-private published package is missing description, keywords, homepage, bugs, author, license, or repository.
  • Record the "every published package fills its npm page" rule in CLAUDE.md.
File Description
scripts/​manifests.test.mjs New test asserting every published (non-private) manifest fills all seven npm-page fields; uses libraryNames to scope and a isBlank helper handling undefined/empty-string/empty-array.
canton-create/​package.json Adds keywords, homepage (GitHub tree URL), bugs, and author.
example-dapps/​amulet-vesting/​package.json Adds the same four fields with amulet/canton-coin keywords.
example-dapps/​token-vesting/​package.json Adds the same four fields with token-standard/canton-token-forge keywords.
CLAUDE.md Documents the npm-page-field requirement and the enforcing test.

Review effort: Balanced

@fernandomg fernandomg moved this from Backlog to In review in Canton - dAppBooster (#390) Oct 30, 2026
Comment thread canton-create/package.json Resolved
Comment thread canton-create/package.json Resolved

This branch was successfully deployed

2 active deployments
Preview – demo.canton-dappbooster — 4f997877 Deployed Oct 30, 2026 by vercel[bot]
Preview – components.canton-dappbooster — 4f997877 Deployed Oct 30, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

Update CN dAppBooster's sub-project's package.json(s) descriptions and metatags where needed

3 participants