apps/humor: move preview tarballs to pnpm.overrides only#2
Conversation
Both server/ and client/ package.json previously listed the preview tarball URLs in BOTH dependencies and pnpm.overrides. pnpm's override resolution is sufficient on its own; the dependencies block now uses canonical ^2.10.0 semvers. Install behavior is unchanged — pnpm.overrides forces the tarball URLs regardless of what dependencies declares. Once @x402/paywall v2.11.x ships on npm with Mezo support, cleanup becomes "delete the overrides block" with zero churn to the dependencies list. Pattern matches the docscrew x402-quickstart doc (hq-wisp-1ldam coordination).
Verification report — install is NOT brokenQuick clarification on the concern raised: the Full post-merge state on
"dependencies": {
"@x402/core": "^2.10.0",
"@x402/evm": "^2.10.0",
"@x402/express": "^2.10.0",
"@x402/paywall": "^2.10.0",
...
},
"pnpm": {
"overrides": {
"@x402/paywall": "https://github.com/vativ/x402-mezo-preview/releases/download/v2.10.0-mezo.6/x402-paywall-2.10.0-mezo.6.tgz",
"@x402/evm": "https://github.com/vativ/x402-mezo-preview/releases/download/v2.10.0-mezo.6/x402-evm-2.10.0-mezo.6.tgz"
}
}
"dependencies": {
"@x402/evm": "^2.10.0",
"@x402/fetch": "^2.10.0",
...
},
"pnpm": {
"overrides": {
"@x402/evm": "https://github.com/vativ/x402-mezo-preview/releases/download/v2.10.0-mezo.6/x402-evm-2.10.0-mezo.6.tgz"
}
}Each of Verification resultsJust ran all three checks on a clean tree at this branch: 1. Fresh
|
|
@ryanRfox — cleared by mayor for your review/merge. Install-safe verification in the previous comment. Feel free to squash or merge-commit; no merge-order dependency with any other branch. |
Summary
Clean up apps/humor's `package.json` files so the two preview tarballs live only in `pnpm.overrides`, not in `dependencies`. Dependencies now use canonical `^2.10.0` semvers.
Addresses the redundancy flagged by docscrew during the x402-quickstart doc coordination (hq-wisp-1ldam) and tracked as `hq-svt48` / `me-e02`.
What changed
Why
pnpm's override resolution forces the tarball URL regardless of what `dependencies` declares, so the duplicate tarball entries in `dependencies` were redundant churn. Keeping them as canonical semvers:
Verification
Test plan