REMOVED · API

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 are now handled internally thanks to strongly typed RPC errors and end users can simply catch them in their application using specific error classes imported from `rpc-errors` sub-path

synced 5h agostrong signal

Removedsince 2026-01-19effective near-api-js 7.0.0

Evidence

Removed in a releasestrongconfirmed in synced data

“Remove no longer needed error utils like `getErrorTypeFromErrorMessage`, `parseRpcError`, `parseResultError`, etc from the package as errors are now handled internally thanks to strongly typed RPC errors and end users can simply catch them in their application using specific error classes imported from `rpc-errors` sub-path”

https://github.com/near/near-api-js/releases/tag/v7.0.0 (opens in a new tab)

2026-01-19

Agents get this entry from check_deprecation("near-api-js-geterrortypefromerrormessage") and GET /api/v1/deprecations/near-api-js-geterrortypefromerrormessage; check_code flags code that uses it. All deprecations →