Packages structure

Dedot's source code is splitted into multiple packages for different purposes, all of the packages and their purposes are listing in the table below.

Packages

Name	Description
@dedot/api	High-level abstraction apis (clients, API executors...)
@dedot/providers	Providers for connection to JSON-RPC servers (WsProvider, SmoldotProvider)
@dedot/types	Generic shared types across the packages
@dedot/runtime-specs	Explicit Runtime API definitions to use for chains only supports Metadata V14
@dedot/shape	Basic codecs/shapes for scale-codec encode/decode
@dedot/contracts	APIs to interact with ink! smart contracts
@dedot/codecs	Known codecs for generic purposes ($Metadata, $AccountId32, $Extrinsic ...)
@dedot/utils	Useful utility functions
@dedot/storage	Storage API for different purposes (caching, ...)
@dedot/codegen	Types & APIs generation engine for chaintypes & ink! smart contracts
@dedot/cli	Dedot's CLI
dedot	Umbrella package re-exporting primitives & APIs from other packages, including subpath packages

dedot subpath packages

By default dedot package only re-exports primitives from @dedot/api, @dedot/providers, @dedot/shape, giving you enough APIs to connect to the network & making on-chain interactions. It also comes with a few subpath packages giving access to APIs to working with ink! contracts, known-codecs, utility functions...

Name	Description
dedot	Re-exports @dedot/api, @dedot/providers & @dedot/shape packages
dedot/contracts	Re-exports @dedot/contracts package
dedot/codecs	Re-exports @dedot/codecs package
dedot/utils	Re-exports @dedot/utils package
dedot/types	Re-exports @dedot/types package
dedot/types/json-rpc	Re-exports @dedot/types/json-rpc package for Substrate JSON-RPC API types information (both new & legacy)
dedot/runtime-specs	Re-exports @dedot/runtime-specs package
dedot/shape	Re-exports @dedot/shape package