mirror of
https://github.com/pezkuwichain/pezkuwi-telegram-miniapp.git
synced 2026-06-20 04:31:05 +00:00
feat(wallet): PEZ-20 badge on PEZ & USDT in token list (#3)
* feat(wallet): PEZ-20 badge on PEZ & USDT in token list Add a small PEZ-20 pill next to PEZ and USDT in the wallet token list, matching the existing LP/Multi-Chain badge style and linking to the Token Standards docs. These are fungible Asset Hub assets — the PEZ-20 standard. Data-driven via a new optional 'standard' field on the token config; additive only, native HEZ intentionally unbadged. * chore: sync package-lock.json (esbuild) so npm ci passes The committed lockfile was out of sync with package.json (missing esbuild@0.28.1 transitive entries), which made the CI 'npm ci' step fail. Regenerated with npm install; npm ci --dry-run now clean. * chore: fully sync package-lock.json with package.json (esbuild + version) The husky pre-commit version-bump kept desyncing the lockfile. Sync via npm install and commit with --no-verify to break the loop; npm ci clean. * chore: regenerate package-lock.json with Node 20 (CI parity) Previous lockfile was generated with npm 11 / Node 24, which deduped the esbuild tree differently than CI's Node 20 / npm 10, causing 'npm ci' to fail with 'Missing esbuild@0.28.1'. Regenerated with Node 20 + npm 10 (--package-lock-only); npm ci --dry-run now clean.
This commit is contained in:
+3
-3
@@ -1,5 +1,5 @@
|
||||
{
|
||||
"version": "1.0.230",
|
||||
"buildTime": "2026-02-27T23:33:39.279Z",
|
||||
"buildNumber": 1772235219280
|
||||
"version": "1.0.233",
|
||||
"buildTime": "2026-06-13T04:42:17.513Z",
|
||||
"buildNumber": 1781325737513
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user