CHECK · DEPRECATIONS

Deprecations

What NEAR has removed, deprecated, changed or replaced, from six signals: archived repositories, README notices, npm and crates.io flags, release-note removals, the docs' own markers and long dormancy. Every entry links its evidence; check_code and check_deprecation answer from this list.

136entries

synced 5h agobuild-deprecations

All136 Removed10 Deprecated121 Superseded1 Changed3 Possibly deprecated1

All136 API5 Config2 Crate1 Package4 Product3 Protocol2 Repository107 RPC method9 Service3

RemovedAPI · checked by hand

WalletConnection and connect() (near-api-js before v7)

Use instead: JsonRpcProvider and Account; @hot-labs/near-connect for browser wallets

DeprecatedAPI · checked by hand

Key stores in near-api-js (keyStores, InMemoryKeyStore and the keystore packages)

Use instead: a KeyPairSigner, or a KeyPairString passed to new Account()

ChangedAPI · checked by hand

actionCreators (near-api-js, @near-js/transactions)

Use instead: actions (addFullAccessKey and addFunctionCallKey instead of addKey)

RemovedAPI · strong signal

getErrorTypeFromErrorMessage and 2 more

near-api-js 7.0.0: Remove no longer needed error utils like `getErrorTypeFromErrorMessage`, `parseRpcError`, `parseResultError`, etc from the package as errors

DeprecatedAPI · strong signal

GasKeyAlreadyExistsActionError and 2 more

near-api-js 7.4.0: deprecate `GasKeyAlreadyExistsActionError`, `GasKeyPermissionInvalidActionError` and `GasKeyTooManyNoncesRequestedActionError`

Showing 5 of 5Check your code from an agent →