mirror of
https://github.com/pezkuwichain/pezkuwi-api.git
synced 2026-10-21 11:16:21 +00:00
Satoshi Qazi Muhammed
611d410f28
The packages/*/package.json files were the manifests the build writes into build/, committed back over the source ones: exports maps of thousands of entries pointing at ./cjs/* files, main at ./cjs/index.js, module and types set. pezkuwi-dev-build-ts generates those fields itself; in the source they pointed at files that only existed because build output had been committed too. main, module, types, exports, browser, react-native and sideEffects are back in the source form of the upstream manifests; every other field is unchanged. - @pezkuwi/* common dependencies 14.0.25 -> 14.0.26 (wasm-crypto 7.5.20 underneath, with working ed25519 and secp256k1) - the root resolutions forcing common 14.0.25 and wasm 7.5.4 onto the whole tree are removed; only the typescript pin remains - @pezkuwi/dev, dev-test and dev-ts ^0.85.12 - the deno script is removed - version 16.5.37
@pezkuwi/api-derive
Collection of high-level utility functions built on top of the @pezkuwi/api library. Designed to simplify the process of querying complex on-chain data by combining multiple RPC calls, storage queries, and runtime logic into a single, callable function.
Instead of manually fetching and processing blockchain data, developers can use api.derive methods to retrieve information.
Available Derive Namespaces
The derive functions are categorized into namespaces based on different common Bizinikiwi modules. Accesible by calling api.derive.NAMESPACE (e.g. api.derive.balances). The available modules are as follows: