[jonathan-nansen]

fromBech32 defaults limit to Infinity and passes it to @scure/base's bech32.decode. Since @scure/base 2.3.0, decode validates limit as a safe integer unless it is false, so every default-argument call (and normalizeBech32) throws:

RangeError: limit: expected safe integer, got Infinity

@cosmjs/encoding depends on @scure/base@^2.0.0, so fresh installs pick up 2.3.0+ and hit this.

bech32.decode has accepted limit: false to disable the length check since 2.0.0 (the limit !== false && length > limit guard is unchanged across 2.0.0–2.4.0). This change maps an omitted limit, and an explicit Infinity for callers who copied the old default, to false. Numeric limits pass through unchanged, and the public signature stays limit?: number.

Tests: the existing long-address test (>90 chars, default limit) covers the regression; added a case passing Infinity explicitly. Note that yarn.lock currently resolves @scure/base@2.0.0, so CI won't reproduce the RangeError without a lockfile bump. I haven't run the suite locally.

Fixes #1982

[greptile-apps]

PR author is not in the allowed authors list.