test: package.json files field excludes scratch dirs, peerDeps version ranges, npm pack dry-run output

[k-deejah]

Problem

Three issues affect package publishing, peer dependencies, and the npm package metadata.

1. sorokit-core and @creit.tech/stellar-wallets-kit are listed as dependencies but should be peerDependencies

A component library should not bundle its peer dependencies. Listing them as dependencies means npm installs a separate copy alongside the consumer's own copy, causing version conflicts and bundle bloat. They should be moved to peerDependencies with compatible version ranges.

2. package.json is missing "files" field — npm publish includes all source files

Without a "files" field, npm publish includes everything in the repo: src/, _issues/, _b/, _c/, and other scratch files. This inflates the published package size and exposes development artefacts to consumers.

3. package.json "keywords" array is missing common search terms

The keywords array has 7 entries but misses: "dapp", "defi", "xlm", "freighter", "wallet-kit", "soroban-contracts". These are frequently searched terms that would improve discoverability on npm.

Solution

1. Move sorokit-core and @creit.tech/stellar-wallets-kit to peerDependencies with ">=0.1.0" ranges.
2. Add "files": ["dist", "README.md", "LICENSE", "CHANGELOG.md"] to package.json.
3. Add the 6 missing keywords to the keywords array.

Acceptance Criteria

• sorokit-core and stellar-wallets-kit in peerDependencies
• "files" field limits publish to dist/, README.md, LICENSE, CHANGELOG.md
• keywords array includes the 6 new search terms
• npm pack --dry-run shows only the expected files
• npm run build passes

---

Note for Contributors: Write a clear PR description. Include the output of npm pack --dry-run before and after the files field change.

[pchieneye]

@pchieneye has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hello, I have reviewed the issue and understand what needs to be done.

I would appreciate being assigned to it.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @pchieneye to this issue.

[tobiadewola41-eng]

@tobiadewola41-eng has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

I would like to work on this

ℹ️ Repo Maintainers: To accept this application, review their application or assign @tobiadewola41-eng to this issue.

[drips-wave]

Congratulations, @tobiadewola41-eng! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

🧑‍💻 @tobiadewola41-eng: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊