open-index/open-npm huggingface dataset:
npm package: @findaway/marketplace
Description: Marketplace Workflows
Author: Findaway
Latest version: 1.0.2

# marketplace-workflows

Marketplace Workflow Scripts

## Commands

-   `create-audition-request-form`
-   `create-audition-requests`
-   `create-project`
-   `list-audition-requests`
-   `login`
-   `project-creator`
-   `set-narrator`
-   `set-project`

## `project-creator`

This command prompts for various details of the project state you'd like to achieve and then performs the necessary requests to create such a project.

When the script prompts for the narrator id you'd like to use, provide a marketplace narrator id (not a proper narrator profile id).

## Getting Started

To run a command, in project root: `node index.js {command}`

E.g. `node index.js project-creator`

## Todos

-   for `project-creator`, move narrator deposit preference to config phase so that script can run without any additional input
npm package: @findaway/prettier-config
Description: Findaway Team Prettier Config
Author: Cameron Wardzala
Latest version: 1.2.0

# `@findaway/prettier-config`

> Findaway Team [Prettier](https://prettier.io) config.

## Usage

**Install**:

```bash
$ yarn add --dev @findaway/prettier-config
```

**Edit `package.json`**:

```jsonc
{
    // ...
    "prettier": "@azz/prettier-config"
}
```
npm package: @finder-stack/client-core
Description: Sample core for higher packages to depend on
Author: CDMBase LLC
Latest version: 0.0.17-12

# Client Core Package
Helper methods and interfaces that can be used by the client part of the packages 

What does it include:
---
    1. exported reducers
    2. exported actions
    3. exported graphql queries
    4. Typescript 2.0.0 => ES6
    5. unit testing with jest

Purpose:
---
    This package can be installable in front-end webserver

What's not included
---
    It does not have any client UI components such as React
    It does have configured Redux Store

Useful commands:
---
    npm run build       - build the library files
    npm run test        - run tests once
    npm run test:watch  - run tests in watchmode (Useful for development)
    
Files explained:
---
     src                         - directory is used for typescript code that is part of the project
        index.ts                 - Index file of the package. Consists of exported reducers and actions
        index.spec.ts            - Tests file for main
        actions                  - Contains Actions to transform the state tree
            index.ts             - References all the exported actions
        reducers                 - Contains reducers, pure function with (state, action) => state signature. 
            index.ts             - References all the exported reducers.
     package.json                - file is used to describe the library and packages that are required added under peer-dependencies section
     tsconfig.json               - configuration file for the library compilation
     webpack.config.js           - configuration file of the compilation automation process for the library
npm package: @finder-stack/client-react
Description: browser plugin for git
Author: CDMBase LLC
Latest version: 0.0.17-39

# React Package
React components and containers

What does it include:
---
    1. exported react pure components
    2. exported react containers
    3. Typescript 2.0.0 => ES6
    4. unit testing with jest

Purpose:
---
This package can be installable in front-end webserver

Useful commands:
---
    npm run build       - build the library files
    npm run test        - run tests once
    npm run test:watch  - run tests in watchmode (Useful for development)
    
Files explained:
---
     src                         - directory is used for typescript code that is part of the project
        index.ts                 - Index file of the package. Consists of exported components and containers
        index.spec.ts            - Tests file for main
        components               - All pure components which don't depend on backend data or external state such as redux
            index.ts             - References all the exported components
        containers               - Components with data to render. Tightly coupled with redux. 
            index.ts             - References all the exported containers
     package.json                - file is used to describe the library and packages that are required added under peer-dependencies section
     tsconfig.json               - configuration file for the library compilation
     webpack.config.js           - configuration file of the compilation automation process for the library


Tutorials:
---
[react-jest-enzymes test](https://www.youtube.com/watch?v=bMmntkVM4wQ)

[testing react with enzyme tutorial](http://codeheaven.io/testing-react-components-with-enzyme/)

[react-redux-typescript-guide](https://github.com/piotrwitek/react-redux-typescript-guide)

Performance:
---
[Redux FAQ: Connecting multiple components](http://redux.js.org/docs/FAQ.html#react-multiple-components)

[React/Redux Links: Performance articles](https://github.com/markerikson/react-redux-links/blob/master/react-performance.md)

[React/Redux: Component re-rendering too often?](http://redux.js.org/docs/faq/ReactRedux.html#react-rendering-too-often)
npm package: @finder-stack/client-redux
Description: GraphQL for sample
Author: CDMBase LLC
Latest version: 0.0.17-12

# Redux Package
Redux npm package includes actions, action-types and reducers

  1. [TypeScript and Redux: getting started][article-1]
  2. [TypeScript and Redux: async actions][article-3]
  3. [TypeScript and Redux: unit testing with Jest][article-4]
  4. [Integrating TypeScript and redux-thunk][article-5]


What does it include:
---
    1. exported reducers
    2. exported actions
    3. exported graphql queries
    4. Typescript 2.0.0 => ES6
    5. unit testing with jest

Purpose:
---
This package can be installable in front-end webserver to use the reducers and actions.

The goal is to make a isolated and reusable module that is self-contained. In order to avoid name conflicts, following rules need to be abide.
1. MUST export a function call reducer()
2. MUST export its action creators as functions
3. MUST have action types in the form `@npm-module-or-app/ACTION_TYPE` eg. `@@finder-stack/INCREMENT_COUNTER`
4. MUST have reducer in the form `npm-module-or-app/reducer_name` eg. `@finder-stack/counter`

What's not included
---
- It does not have any client UI components such as React
- It does not configure Redux Store

Useful commands:
---
    npm run build       - build the library files
    npm run test        - run tests once
    npm run test:watch  - run tests in watchmode (Useful for development)
    
Files explained:
---
     src                         - directory is used for typescript code that is part of the project
        index.ts                 - Index file of the package. Consists of exported reducers and actions
        index.spec.ts            - Tests file for main
        actions                  - Contains Actions to transform the state tree
            index.ts             - References all the exported actions
        reducers                 - Contains reducers, pure function with (state, action) => state signature. 
            index.ts             - References all the exported reducers.
     package.json                - file is used to describe the library and packages that are required added under peer-dependencies section
     tsconfig.json               - configuration file for the library compilation
     webpack.config.js           - configuration file of the compilation automation process for the library
                 

[article-1]: https://rjzaworski.com/2016/08/getting-started-with-redux-and-typescript
[article-2]: https://rjzaworski.com/2016/08/typescript-redux-and-react
[article-3]: https://rjzaworski.com/2016/09/typescript-redux-async-actions
[article-4]: https://rjzaworski.com/2016/12/testing-typescript-with-jest
[article-5]: https://rjzaworski.com/2017/01/typescript-redux-thunk
npm package: @finder-stack/client-state
Description: GraphQL for sample
Author: CDMBase LLC
Latest version: 0.0.17-39

# Redux Package
Redux npm package includes actions, action-types and reducers

  1. [TypeScript and Redux: getting started][article-1]
  2. [TypeScript and Redux: async actions][article-3]
  3. [TypeScript and Redux: unit testing with Jest][article-4]
  4. [Integrating TypeScript and redux-thunk][article-5]


What does it include:
---
    1. exported reducers
    2. exported actions
    3. exported graphql queries
    4. Typescript 2.0.0 => ES6
    5. unit testing with jest

Purpose:
---
This package can be installable in front-end webserver to use the reducers and actions.

The goal is to make a isolated and reusable module that is self-contained. In order to avoid name conflicts, following rules need to be abide.
1. MUST export a function call reducer()
2. MUST export its action creators as functions
3. MUST have action types in the form `@npm-module-or-app/ACTION_TYPE` eg. `@@finder-stack/INCREMENT_COUNTER`
4. MUST have reducer in the form `npm-module-or-app/reducer_name` eg. `@finder-stack/counter`

What's not included
---
- It does not have any client UI components such as React
- It does not configure Redux Store

Useful commands:
---
    npm run build       - build the library files
    npm run test        - run tests once
    npm run test:watch  - run tests in watchmode (Useful for development)
    
Files explained:
---
     src                         - directory is used for typescript code that is part of the project
        index.ts                 - Index file of the package. Consists of exported reducers and actions
        index.spec.ts            - Tests file for main
        actions                  - Contains Actions to transform the state tree
            index.ts             - References all the exported actions
        reducers                 - Contains reducers, pure function with (state, action) => state signature. 
            index.ts             - References all the exported reducers.
     package.json                - file is used to describe the library and packages that are required added under peer-dependencies section
     tsconfig.json               - configuration file for the library compilation
     webpack.config.js           - configuration file of the compilation automation process for the library
                 

[article-1]: https://rjzaworski.com/2016/08/getting-started-with-redux-and-typescript
[article-2]: https://rjzaworski.com/2016/08/typescript-redux-and-react
[article-3]: https://rjzaworski.com/2016/09/typescript-redux-async-actions
[article-4]: https://rjzaworski.com/2016/12/testing-typescript-with-jest
[article-5]: https://rjzaworski.com/2017/01/typescript-redux-thunk
npm package: @finder-stack/graphql-schema
Description: Sample Schema Module
Author: CDMBase LLC
Latest version: 0.0.17-12

# @finder-stack/graphql-schema
This package is intended to be used with [Apollo Server](http://docs.apollostack.com/apollo-server/tools.html) to provide an easy way to setup a GraphQL server and connect it to your database. Note that Apollo Server is not a depenedency of this package. 

Usage
---

Sample Schema exports four things: **database**, **resolvers**, **subscriptions** and **typeDefs**.


*resolvers*
Resolvers are functions that tell the server how to find and return the data for each field in a GraphQL query. The resolving functions simply call your Database Connectors by passing in parameters and return the Connectors result (usually a Promise).

After creating your Database and Connectors from Database, you can call the resolvers function by passing in the Connectors and your public application settings (since settings are stored in the application state). Building on the previous examples:

*typeDefs* is a GraphQL Schema based on the queries provided to it from database. With the schema, you can do things like Find Posts by post_type, get the Postmeta of a Post by the post_id, and so on.

*subscriptions* 
GraphQL subscriptions allow developers to introduce new levels of interactivity to their apps with near-realtime updates. You can keep your app updated to the latest changes (that you subscribe to) between different users:

*database*
The first part of Sample Schema is **database**. This class provides an easy connection to your database using some connection settings, explained below.


Files explained:
---
     src                         - directory is used for typescript code that is part of the project
        index.ts                 - Index file of the package. Consists of exported components and containers
        index.spec.ts            - Tests file for main
        modules                  - Fractal route for server-side application module splitting (schema definition, resolvers, subscription filters, database connectors )
     package.json                - file is used to describe the library and packages that are required added under peer-dependencies section
     tsconfig.json               - configuration file for the library compilation
     webpack.config.js           - configuration file of the compilation automation process for the library


Setup
---
`modules` directory consists of the sub directories based on the criteria for module splitting. Each sub-directory may have schema definition, resolvers, subscriptions, database

Schema definition files should have suffix as `.graphql` or `.graphqls`. Resolvers file should be named as `resolvers.ts` and subscriptions filter file as `subscriptions.ts`.

All the files under modules are automatically bundled when you run `npm run build`, so the above naming convention should be followed.

## Reference:
https://github.com/ramsaylanier/WordExpressSchema
npm package: @finder-stack/hemera-counter
Description: This is Container Configuration Service hemera plugin
Latest version: 0.0.5

# hemera-counter

Your plugin description

# Prerequisites

[Install and run NATS Server](http://nats.io/documentation/tutorials/gnatsd-install/)

# Example

```js
'use strict'

const Hemera = require('nats-hemera')
const plugin = require('hemera-counter')
const nats = require('nats').connect()

const hemera = new Hemera(nats, {
  logLevel: 'info'
})

hemera.use(plugin)

hemera.ready(() => {
  hemera.act({
    topic: 'counter',
    cmd: 'add',
    a: 1,
    b: 2
  }, function (err, resp) {
    this.log.info(resp, 'Result')
  })
})

```

# Test

```
npm run test
```

# Code coverage

```
npm run coverage
```

# Linting

```
npm run lint
```
npm package: @finder-stack/hemera-plugin
Description: This is Container Configuration Service hemera plugin
Latest version: 0.0.17-39

# hemera-plugin

Your plugin description

# Prerequisites

[Install and run NATS Server](http://nats.io/documentation/tutorials/gnatsd-install/)

# Example

```js
'use strict'

const Hemera = require('nats-hemera')
const plugin = require('hemera-plugin')
const nats = require('nats').connect()

const hemera = new Hemera(nats, {
  logLevel: 'info'
})

hemera.use(plugin)

hemera.ready(() => {
  hemera.act({
    topic: 'counter',
    cmd: 'add',
    a: 1,
    b: 2
  }, function (err, resp) {
    this.log.info(resp, 'Result')
  })
})

```

# Test

```
npm run test
```

# Code coverage

```
npm run coverage
```

# Linting

```
npm run lint
```
npm package: @finder-stack/microservice-hemera-plugin
Description: This is Container Configuration Service hemera plugin
Latest version: 0.0.5

# hemera-container-manager

Your plugin description

# Requirements

Make sure to set following environment properties

```
    process.env.CLOUDFLARE_EMAIL,
    process.env.CLOUDFLARE_KEY,
    process.env.CLOUDFLARE_ZONE_ID,
```
# Prerequisites

[Install and run NATS Server](http://nats.io/documentation/tutorials/gnatsd-install/)

# Example

```js
'use strict'

const Hemera = require('nats-hemera')
const Plugin = require('hemera-container-manager')
const nats = require('nats').connect()

const hemera = new Hemera(nats, {
  logLevel: 'info'
})

hemera.use(Plugin)

hemera.ready(() => {
  hemera.act({
    topic: 'container-manager',
    cmd: 'add',
    a: 1,
    b: 2
  }, function (err, resp) {
    this.log.info(resp, 'Result')
  })
})

```

# Test

```
npm run test
```

# Code coverage

```
npm run coverage
```

# Linting

```
npm run lint
```
npm package: @finder-stack/microservice-nats
Description: This is Container Configuration Service hemera plugin
Latest version: 0.0.17-39

# hemera-container-manager

Your plugin description

# Requirements

Make sure to set following environment properties

```
    process.env.CLOUDFLARE_EMAIL,
    process.env.CLOUDFLARE_KEY,
    process.env.CLOUDFLARE_ZONE_ID,
```
# Prerequisites

[Install and run NATS Server](http://nats.io/documentation/tutorials/gnatsd-install/)

# Example

```js
'use strict'

const Hemera = require('nats-hemera')
const Plugin = require('hemera-container-manager')
const nats = require('nats').connect()

const hemera = new Hemera(nats, {
  logLevel: 'info'
})

hemera.use(Plugin)

hemera.ready(() => {
  hemera.act({
    topic: 'container-manager',
    cmd: 'add',
    a: 1,
    b: 2
  }, function (err, resp) {
    this.log.info(resp, 'Result')
  })
})

```

# Test

```
npm run test
```

# Code coverage

```
npm run coverage
```

# Linting

```
npm run lint
```
npm package: @findeth/abi
Description: A tiny Solidity ABI encoder and decoder
Author: Maarten Zuidhoorn
Latest version: 0.7.1

# `@findeth/abi`

![Version](https://img.shields.io/npm/v/@findeth/abi) ![License](https://img.shields.io/github/license/FindETH/abi) [![GitHub CI](https://github.com/FindETH/abi/workflows/CI/badge.svg)](https://github.com/FindETH/abi/actions) [![codecov](https://codecov.io/gh/FindETH/abi/branch/master/graph/badge.svg)](https://codecov.io/gh/FindETH/abi)

`@findeth/abi` is a zero-dependencies ABI encoder and decoder library for FindETH. It supports both Node.js and web browsers. **This library is experimental**, and may not work with all contract interfaces. It is used in the FindETH applications, that can be found here:

- [Web](https://github.com/FindETH/web)

Currently, most types (except fixed-point numbers (`fixed<M>x<N>`), and fixed-length arrays `type<M>`) are supported.

**Note**: This is a work-in-progress version of FindETH, and is **not** production-ready. For the current version of FindETH, please refer to [this repository](https://github.com/Mrtenz/FindETH/tree/master). The public API _may_ change in minor releases below 1.0.0 (though this is unlikely).

---

## Installation

You can install `@findeth/abi` with Yarn (recommended) or NPM:

```
$ yarn add @findeth/abi
```

```
$ npm install @findeth/abi
```

**Note**: If you are using TypeScript, `@findeth/abi` requires TypeScript 4.1 or newer. This is used for automatically inferring the types of the input and output, based on the specified `types`.

## Getting Started

You can use the `encode` and `decode` functions to encode and decode ABI respectively.

### Encode

The encode function takes an array of ABI types (e.g., `["string", "uint256"]`) and an array of values to encode. For example:

```ts
import { encode, toHex } from "@findeth/abi";

const buffer = encode(["string", "uint256"], ["foo bar", 12345]);
console.log(toHex(buffer));

// 000000000000000000000000000000000000000000000000000000000000004000000000000000000000000000000000000000000000000000000000000030390000000000000000000000000000000000000000000000000000000000000007666f6f2062617200000000000000000000000000000000000000000000000000
```

### Decode

The decode function takes an array of ABI types, and a buffer (`Uint8Array`) to decode. Note that Node.js `Buffer`s are compatible with `Uint8Array`, but in order to maintain full compatibility with web browsers (without the need for polyfills), this library does not use `Buffer`. Example:

```ts
import { decode, fromHex } from "@findeth/abi";

const value = fromHex("000000000000000000000000000000000000000000000000000000000000004000000000000000000000000000000000000000000000000000000000000030390000000000000000000000000000000000000000000000000000000000000007666f6f2062617200000000000000000000000000000000000000000000000000");
console.log(decode(["string", "uint256"], value));

// ["foo bar", 12345n]
```

## Development

Install dependencies with `yarn`:

```
$ yarn
```

To run automated tests, use the `test` script:

```
$ yarn test
```


To build the library, use the `build` script:

```
$ yarn build
```
npm package: @findeth/hdnode
Description: Small HD wallet key derivation library
Author: Maarten Zuidhoorn
Latest version: 0.6.1

# `@findeth/hdnode`

![Version](https://img.shields.io/npm/v/@findeth/hdnode) ![License](https://img.shields.io/github/license/FindETH/hdnode) [![Travis CI](https://travis-ci.com/FindETH/hdnode.svg?branch=master)](https://travis-ci.com/FindETH/hdnode) [![codecov](https://codecov.io/gh/FindETH/hdnode/branch/master/graph/badge.svg)](https://codecov.io/gh/FindETH/hdnode)


`@findeth/hdnode` is a library used by FindETH, used for mnemonic phrases and HD wallet key derivation. It is used in the desktop, web and CLI applications, that can be found here:

- [Desktop](https://github.com/FindETH/desktop)
- [Web](https://github.com/FindETH/web)
- [CLI](https://github.com/FindETH/cli)

**Note**: This is a work-in-progress version of FindETH, and is **not** production-ready. For the current version of FindETH, please refer to [this repository](https://github.com/Mrtenz/FindETH/tree/master).

---

## Installation

You can install `@findeth/hdnode` with Yarn (recommended) or NPM:

```
$ yarn add @findeth/hdnode
```

```
$ npm install @findeth/hdnode
```

## Getting Started

TODO

## Development

Install dependencies with `yarn`:

```
$ yarn
```

To run automated tests, use the `test` script:

```
$ yarn run lint
```


To build the library, use the `build` script:

```
$ yarn run build
```
npm package: @findeth/networks
Description: Network functionality used by FindETH
Author: Maarten Zuidhoorn
Latest version: 0.6.2

# `@findeth/networks`

![Version](https://img.shields.io/npm/v/@findeth/networks) ![License](https://img.shields.io/github/license/FindETH/networks) [![Travis CI](https://travis-ci.com/FindETH/networks.svg?branch=master)](https://travis-ci.com/FindETH/networks) [![codecov](https://codecov.io/gh/FindETH/networks/branch/master/graph/badge.svg)](https://codecov.io/gh/FindETH/networks)


`@findeth/networks` is a library used by FindETH, which provides network functionality. It is used in the desktop, web and CLI applications, that can be found here:

- [Desktop](https://github.com/FindETH/desktop)
- [Web](https://github.com/FindETH/web)
- [CLI](https://github.com/FindETH/cli)

**Note**: This is a work-in-progress version of FindETH, and is **not** production-ready. For the current version of FindETH, please refer to [this repository](https://github.com/Mrtenz/FindETH/tree/master).

---

## Installation

You can install `@findeth/networks` with Yarn (recommended) or NPM:

```
$ yarn add @findeth/networks
```

```
$ npm install @findeth/networks
```

## Getting Started

TODO

## Development

Install dependencies with `yarn`:

```
$ yarn
```

To run automated tests, use the `test` script:

```
$ yarn run lint
```


To build the library, use the `build` script:

```
$ yarn run build
```
npm package: @findeth/secp256k1
Description: Tiny SECP256k1 and ECDSA implementation
Author: Maarten Zuidhoorn
Latest version: 0.3.1

# `@findeth/secp256k1`

![Version](https://img.shields.io/npm/v/@findeth/secp256k1) ![License](https://img.shields.io/github/license/FindETH/secp256k1) [![Travis CI](https://travis-ci.com/FindETH/secp256k1.svg?branch=master)](https://travis-ci.com/FindETH/secp256k1) [![codecov](https://codecov.io/gh/FindETH/secp256k1/branch/master/graph/badge.svg)](https://codecov.io/gh/FindETH/secp256k1)


`@findeth/secp256k1` is a tiny SECP256k1 and ECDSA implementation used by FindETH. It is used in the desktop, web and CLI applications, that can be found here:

- [Desktop](https://github.com/FindETH/desktop)
- [Web](https://github.com/FindETH/web)
- [CLI](https://github.com/FindETH/cli)

**Note**: This is a work-in-progress version of FindETH, and is **not** production-ready. For the current version of FindETH, please refer to [this repository](https://github.com/Mrtenz/FindETH/tree/master).

---

## Installation

You can install `@findeth/secp256k1` with Yarn (recommended) or NPM:

```
$ yarn add @findeth/secp256k1
```

```
$ npm install @findeth/secp256k1
```

## Getting Started

TODO

## Development

Install dependencies with `yarn`:

```
$ yarn
```

To run automated tests, use the `test` script:

```
$ yarn run test
```


To build the library, use the `build` script:

```
$ yarn run build
```
npm package: @findeth/wallets
Description: Library used by FindETH for wallets and derivation
Author: Maarten Zuidhoorn
Latest version: 0.5.2

# `@findeth/wallets`

![Version](https://img.shields.io/npm/v/@findeth/wallets) ![License](https://img.shields.io/github/license/FindETH/wallets) [![Travis CI](https://travis-ci.com/FindETH/wallets.svg?branch=master)](https://travis-ci.com/FindETH/wallets) [![codecov](https://codecov.io/gh/FindETH/wallets/branch/master/graph/badge.svg)](https://codecov.io/gh/FindETH/wallets)


`@findeth/wallets` is a library used by FindETH, which provides wallet and address derivation functionality. It is used in the desktop, web and CLI applications, that can be found here:

- [Desktop](https://github.com/FindETH/desktop)
- [Web](https://github.com/FindETH/web)
- [CLI](https://github.com/FindETH/cli)

**Note**: This is a work-in-progress version of FindETH, and is **not** production-ready. For the current version of FindETH, please refer to [this repository](https://github.com/Mrtenz/FindETH/tree/master).

---

## Installation

You can install `@findeth/wallets` with Yarn (recommended) or NPM:

```
$ yarn add @findeth/wallets
```

```
$ npm install @findeth/wallets
```

## Getting Started

TODO

## Development

Install dependencies with `yarn`:

```
$ yarn
```

To run automated tests, use the `test` script:

```
$ yarn run lint
```


To build the library, use the `build` script:

```
$ yarn run build
```