### Description
- Replace use of debug lib with Pino
- Replace `loggerName` params with Logger types
- Update SDK Readme
### Related issues
Fixes https://github.com/hyperlane-xyz/issues/issues/918
### Backward compatibility
No, breaks anyone passing in custom logger to SDK classes, which is likely no one
### Testing
- Tested in CLI
- Tested in Warp UI
The Hyperlane SDK helps developers create and manage interchain applications.
For details on how to use the various abstractions and utilities, [see the documentation](https://docs.hyperlane.xyz/docs/sdks/building-applications)
For more details on Hyperlane concepts, [see the documentation](https://docs.hyperlane.xyz)
## Install
@ -20,9 +20,15 @@ yarn add @hyperlane-xyz/sdk
The names and relevant metadata for all Hyperlane-supported chains are included in this SDK, including public RPC and Explorer urls. It also includes the addresses for all Hyperlane core contracts and middleware.
### Deployment, testing, and development classes
### Classes for development, deployment, and testing
Classes for deploying, testing, and building applications using Hyperlane are included in the SDK. See [the docs](https://docs.hyperlane.xyz/docs/sdks/building-applications/nodejs-sdk) for details.
The SDK includes various classes for building, deploying, and testing multi-chain applications. Different abstractions serve different use cases. A few common utilities include:
- `MultiProvider` / `MultiProtocolProvider`: A utility for managing chain metadata, and RPC providers.
- `HyperlaneApp` / `MultiProtocolApp`: A base to extend for a multi-chain app.
- `HyperlaneCore` / `MultiProtocolCore`: A class for common interactions with Hyperlane core deployments.
- `HyperlaneDeployer`: The base class for executing multi-chain contract deployments.
- `Token`&`WarpCore`: Utilities for interacting with Warp Route deployments.