2.5.9 • Published 7 months ago

@readyio/ready-lib v2.5.9

Weekly downloads
-
License
ISC
Repository
-
Last release
7 months ago

Ready Lib

Installing Ready Lib for a project

  • Add ready lib dependencies via gitlab: Modify package.json as

    "dependencies": {
        "ready-lib": "git+https://git.cystack.org/ready/ready-lib.git"
    }
  • Install with npm

    npm install

    or with yarn

    yarn
  • Reintall library when there's new version

    npm install ready-lib -f

Usage

  • Import readylib to invoke essential methods. E.g., to get transaction history of a Polygon wallet:

    import {readylib} from '@readyio/ready-lib'
    const txns = await readylib.queryAllTransactions("0x1b0f42570c8b32a1023cb33e1a1eaa4a1f0d8d4a", readylib.ChainId.POLYGON, {
        limit: 20,
        from: "19964669",
        to: "19981387"
    })
  • On the other hand, exported methods and types can also be called directly without readylib import

Get started for developing Ready Lib

Prerequisite:

  1. Node.js
  2. Yarn/Npm
  3. pre-commit

Steps

  1. Download dependencies with yarn or npm

    yarn
    • Note that, as a library's perspective, package.json is the single source of truth and developers should not rely on package-lock.json or yarn.lock to re-create the same environment. A good practice is to delete those lock files & node_modules and then reinstall dependencies to test if package.json is good to go.
  2. Installing pre-commit hooks (for god's sake, we should avoid commiting & pushing those stealthy secrets asap)

    pre-commit install

Quick Nodes (todo: categorize these notes)

  • Use *.spec.ts for quickly testing our modules. We will add more cases in the future. The code base now is not in good coverage yet.
  • Put secrets concentrating in a place for easier ignoring pushing them.
  • For mock data that we're afraid of being catched by gitleaks, use .gitleaksignore

TODO:

Development Helpers

  1. add more tests (both happy & unhappy cases)
  2. auto install pre-commit hooks between team members
  3. config example folder for a greater usability
  4. add dependency bot for real-time alert

CI/CD

  1. run all unit tests before merging
  2. run examples as a test pipeline
2.5.4

11 months ago

2.5.3

11 months ago

2.5.5

10 months ago

2.5.8

7 months ago

2.5.7

9 months ago

2.5.9

7 months ago

2.5.2

12 months ago

2.5.1

12 months ago

2.5.0

1 year ago

2.4.3

1 year ago

2.4.2

1 year ago

2.4.1

1 year ago

2.4.0

1 year ago

2.3.9

1 year ago

2.3.11

1 year ago

2.3.10

1 year ago

2.3.8

1 year ago

2.2.1

1 year ago

2.3.2

1 year ago

2.3.1

1 year ago

2.3.4

1 year ago

2.3.3

1 year ago

2.3.6

1 year ago

2.3.5

1 year ago

2.3.7

1 year ago

2.0.7

2 years ago

2.0.4

2 years ago