Skip to content

Fix package.json metadata (description, license, repo links) - #74

Open
phwizard wants to merge 1 commit into
mainfrom
chore/package-json-metadata
Open

Fix package.json metadata (description, license, repo links)#74
phwizard wants to merge 1 commit into
mainfrom
chore/package-json-metadata

Conversation

@phwizard

Copy link
Copy Markdown
Member

Cleanup of package.json fields that were either wrong or missing — these surface on the npm package page and are read by directory/listing crawlers.

Changes

Field Before After
description a garbled npm create vite... install snippet a proper one-line summary
license "AGPL" "MIT"
homepage (missing) https://playground.chat.ethora.com
repository (missing) the GitHub repo
bugs (missing) the issues URL
keywords 9 keys incl. messenger, web3 aligned with the GitHub repo topics

Note on the license change

This is a metadata correction, not a relicensing. The repo's LICENSE file is the standard MIT License (Copyright (c) 2025 Dappros Ltd), and the GitHub repo is detected as MIT. package.json said "AGPL", which both contradicts that file and isn't a valid SPDX identifier. This change makes package.json agree with the existing LICENSE file.

Why now

The npm page currently shows no repository link and a nonsense description, which weakens the package on npm and blocks clean submission to component directories. No code changes — metadata only.

- description: was a garbled install snippet; now a proper one-line summary
- license: was "AGPL" (invalid SPDX, and contradicts the MIT LICENSE file
  in the repo) → corrected to "MIT"
- add homepage, repository, and bugs fields (were missing — npm showed no
  repo link)
- keywords: align with the GitHub repo topics
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