open-index/open-npm huggingface dataset:
npm package: @pezkuwi/api-derive
Description: Common functions used across Pezkuwi, derived from RPC calls and storage queries.
Author: PezkuwiChain
Latest version: 16.5.36

# @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:

- [accounts](https://github.com/pezkuwichain/pezkuwi-api/tree/master/packages/api-derive/src/accounts)
- [alliance](https://github.com/pezkuwichain/pezkuwi-api/tree/master/packages/api-derive/src/alliance)
- [bagsList](https://github.com/pezkuwichain/pezkuwi-api/tree/master/packages/api-derive/src/bagsList)
- [balances](https://github.com/pezkuwichain/pezkuwi-api/tree/master/packages/api-derive/src/balances)
- [bounties](https://github.com/pezkuwichain/pezkuwi-api/tree/master/packages/api-derive/src/bounties)
- [chain](https://github.com/pezkuwichain/pezkuwi-api/tree/master/packages/api-derive/src/chain)
- [contracts](https://github.com/pezkuwichain/pezkuwi-api/tree/master/packages/api-derive/src/contracts)
- [council](https://github.com/pezkuwichain/pezkuwi-api/tree/master/packages/api-derive/src/council)
- [crowdloan](https://github.com/pezkuwichain/pezkuwi-api/tree/master/packages/api-derive/src/crowdloan)
- [democracy](https://github.com/pezkuwichain/pezkuwi-api/tree/master/packages/api-derive/src/democracy)
- [elections](https://github.com/pezkuwichain/pezkuwi-api/tree/master/packages/api-derive/src/elections)
- [imOnline](https://github.com/pezkuwichain/pezkuwi-api/tree/master/packages/api-derive/src/imOnline)
- [membership](https://github.com/pezkuwichain/pezkuwi-api/tree/master/packages/api-derive/src/membership)
- [teyrchains](https://github.com/pezkuwichain/pezkuwi-api/tree/master/packages/api-derive/src/teyrchains)
- [session](https://github.com/pezkuwichain/pezkuwi-api/tree/master/packages/api-derive/src/session)
- [society](https://github.com/pezkuwichain/pezkuwi-api/tree/master/packages/api-derive/src/society)
- [staking](https://github.com/pezkuwichain/pezkuwi-api/tree/master/packages/api-derive/src/staking)
- [technicalCommittee](https://github.com/pezkuwichain/pezkuwi-api/tree/master/packages/api-derive/src/technicalCommittee)
- [treasury](https://github.com/pezkuwichain/pezkuwi-api/tree/master/packages/api-derive/src/treasury)
- [tx](https://github.com/pezkuwichain/pezkuwi-api/tree/master/packages/api-derive/src/tx)
npm package: @pezkuwi/dev-test
Description: A basic test-functions-as-global library on top of node:test
Author: Pezkuwi Team
Latest version: 0.85.7

# @pezkuwi/dev-test

This is a very basic Jest-compatible environment that could be used alongside tests. The need for this came from replacing Jest with `node --test` without rewriting all assertions.

It provides the following -

1. Browser `window`, `document`, `navigator` (see usage for browser-specific path)
2. `jest` functions, specifically `spyOn` (not comprehensive, some will error, some witll noop)
3. `expect` functions (not comprehensive, caters for specific pezkuwi-js usage)


## Usage

On thing to note is that `node:test` is still rapidly evolving - this includes the APIs and features. As such this requires at least Node 18.14, however 18.15+ is recommended.

The entry points are different based on the environment you would like to operate in. For a browser-like environment,

```
node --require @pezkuwi/dev-test/browser ...
```

or for a basic describe/expect/jest-only global environment

```
node --require @pezkuwi/dev-test/node ...
```

The `...` above indicates any additional Node options, for instance a full command could be -

```
node --require @pezkuwi/dev-test/node --test something.test.js
```
npm package: @pezkuwi/extension-base
Description: Functions, classes and other utilities used in @pezkuwi/extension
Author: Kurdistan Tech Institute
Latest version: 0.62.19

# @polkadot/extension-base

Functions, classes and other utilities used in `@polkadot/extension`. These include:
- background script handlers,
- message passing,
- scripts injected inside pages.

They are primarily meant to be used in `@polkadot/extension`, and can be broken without any notice to cater for `@polkadot/extension`'s needs.

They are exported here if you wish to use part of them in the development of your 
own extension. Don't forget to add `process.env.EXTENSION_PREFIX` to separate 
ports and stores from the current extension's ones.
npm package: @pezkuwi/extension-inject
Description: A generic injector (usable to any extension), that populates the base exposed interfaces to be used by dapps.
Author: Kurdistan Tech Institute
Latest version: 0.62.20

# @polkadot/extension-inject

This is a basic extension injector that manages access to the global objects available. As an extension developer, you don't need to manage access to the window object manually, by just calling  enable here, the global object is setup and managed properly. From here any dapp can access it with the `@polkadot/extension-dapp` package;

## Usage

```js
import { injectExtension } from '@polkadot/extension-inject';

// this a the function that will be exposed to be callable by the dapp. It resolves a promise
// with the injected interface, (see `Injected`) when the dapp at `originName` (url) is allowed
// to access functionality
function enableFn (originName: string): Promise<Injected> {
  ...
}

// injects the extension into the page
injectExtension(enableFn, { name: 'myExtension', version: '1.0.1' });
```
npm package: @pezkuwi/keyring
Description: Keyring management
Author: Dijital Kurdistan Tech Institute
Latest version: 14.0.25

# @pezkuwi/keyring

Key management of user accounts including generation and retrieval of keyring pairs from a variety of input combinations.

## Usage

Installation -

```
yarn add @pezkuwi/keyring
```

Classes and Functions can be imported as follows:

```js
import Keyring from '@pezkuwi/keyring';
```