fix(deps): update dependency pako to v3

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
pako	2.1.0 → 3.0.1
@​types/pako	2.0.4 → 3.0.0

---

Release Notes

nodeca/pako (pako)

v3.0.1

Compare Source

Changed

• Narrow Uint8Array type to ArrayBuffer only
• Added Z_STREAM_ERROR check (reachable only via wrong options call)

v3.0.0

Compare Source

Added

• Generated type definitions.
• Low-level zlib API exports.
• .onStart() hooks for advanced stream setup.

Changed

• Switched sources to TypeScript, and tests, examples and benchmarks to ESM.
• Changed exports to named-only. Use import * as pako from 'pako' instead of
  default import if you need the whole API as an object.
• Changed package files layout. See package.json for supported entry points.
• legacyHash default is now false. Binary output is now compatible with
  nodejs by default.
• dictionary option now accepts only Uint8Array / ArrayBuffer
  (no String anymore).
• .onEnd() now only assembles output chunks into result, and no longer sets
  the err / msg fields.
• Use native TextEncoder / TextDecoder for string conversion. Removed shims.
• Replaced { to: 'string' }) with { toText: true }) for UTF-8 text output in
  high-level helpers (inflate, inflateRaw, ungzip).
• Build dist/ on publish instead of keeping generated bundles in git.
• Inflate.push() after stream end returns the decode result, not always
  false.

Removed

• Default export. import pako from 'pako' is no longer supported.
• { to: 'string' }) option from the streaming Inflate class. It now always
  emits byte chunks.
• Automatic gzip header collection in Inflate. Use .onStart() with
  zlibInflateGetHeader() to read gzip metadata.
• Prebuilt dist/ bundles from repository.

v2.2.0

Compare Source

Added

• Alternate deflate hash (ANZAC++) - for nodejs zlib compatibility.
  A nice bonus ~ 40% speed boost.
• legacyHash (default: true) deflate option, to switch between original zlib
  and nodejs binary-compatible output.

Fixed

• Inflate: fix window not updated after inflateReset (multistream/bgzip), #​139.
• Inflate: emit chunk on flush, #​259.
• Inflate: only continue to next stream for gzip; error on truncated input.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[netlify]

👷 Deploy Preview for aptos-explorer processing.

Name	Link
🔨 Latest commit	57b3d67
🔍 Latest deploy log	https://app.netlify.com/projects/aptos-explorer/deploys/6a7243d66f197a0008623850

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pnpm-lock.yaml

✓ Lockfile passes supply-chain policies (verified 1m ago)
Progress: resolved 1, reused 0, downloaded 0, added 0
[WARN] deprecated @types/pako@3.0.0: This is a stub types definition. pako provides its own type definitions, so you do not need this installed.
Progress: resolved 169, reused 0, downloaded 0, added 0
Progress: resolved 350, reused 0, downloaded 0, added 0
Progress: resolved 582, reused 0, downloaded 0, added 0
Progress: resolved 1128, reused 0, downloaded 0, added 0
[WARN] deprecated @telegram-apps/bridge@1.9.2: This package is not supported anymore. Use @tma.js/bridge instead
[ERR_PNPM_NO_MATURE_MATCHING_VERSION] 1 version does not meet the minimumReleaseAge constraint:
  @types/pako@3.0.0 was published at 2026-08-04T22:28:54.189Z, within the minimumReleaseAge cutoff (2026-07-30T23:40:38.868Z)