open-index/open-npm huggingface dataset:
npm package: @monopolyswap/sdk
Description: 🛠 An SDK for building applications on top of MonopolySwap.
Latest version: 1.0.15

# Sushiswap SDK

In-depth documentation on this SDK is available at [uniswap.org](https://uniswap.org/docs/v2/SDK/getting-started/).

This modifies uniswap-sdk's UniswapV2Factory address. The new address for sushiswap is  `0xC0AEe478e3658e2610c5F7A4A2E1777cE9e4f2Ac`.

## Running tests

To run the tests, follow these steps. You must have at least node v10 and [yarn](https://yarnpkg.com/) installed.

First clone the repository:

```sh
git clone https://github.com/sushiswap/sushiswap-sdk.git
```

Move into the sushiswap-sdk working directory

```sh
cd sushiswap-sdk/
```

Install dependencies

```sh
yarn install
```

Run tests

```sh
yarn test
```

You should see output like the following:

```sh
yarn run v1.22.4
$ tsdx test
 PASS  test/constants.test.ts
 PASS  test/pair.test.ts
 PASS  test/fraction.test.ts
 PASS  test/miscellaneous.test.ts
 PASS  test/entities.test.ts
 PASS  test/trade.test.ts

Test Suites: 1 skipped, 6 passed, 6 of 7 total
Tests:       3 skipped, 82 passed, 85 total
Snapshots:   0 total
Time:        5.091s
Ran all test suites.
✨  Done in 6.61s.
```
npm package: @monordo/bitfield-permission-manager
Description: MonOrdo library for manage permissions with bitfield system
Author: Cariz
Latest version: 0.0.14

# bitfield-permission-manager
![badge][0] [![Build Status][1]][2]

![MonOrdo logo](https://www.monordo.com/wp-content/uploads/2022/06/MonOrdo.jpg)

❤️ **This library is developed and maintained by MonOrdo** ❤️

This library is developed to use the [Bit field](https://en.wikipedia.org/wiki/Bit_field) method as the main logic base within our permission system. We did not invent this method, nor its application to the permission system, but after having been inspired by discord, for example. We chose to simplify its use by creating a library to apply it more simply. This library supports [injection](https://rxjs.dev/) within a module and can therefore be injected, for example, within the services of a [NestJs](https://nestjs.com/) server. This library also exposes a Guard to simplify its use within [NestJs](https://nestjs.com/).

The bit field method allows building a permission system like Discord uses for its channels. The main advantage is to avoid heavy data transfers on the whole proposed solution. For its use, the storage of a big int is enough. The second advantage is its reliability for the check of permissions, no storage of permissions is necessary except the storage of the big int, so only its interpretation can differ in time and not name migrations as can be found on classical methods.

**Repository:** [https://github.com/monordo/bitfield-permission-manager](https://github.com/monordo/bitfield-permission-manager)

**Official documentation:** [https://monordo.gitbook.io/bitfield-permission-manager/](https://monordo.gitbook.io/bitfield-permission-manager/)

**NPM details:** [https://www.npmjs.com/package/@monordo/bitfield-permission-manager](https://www.npmjs.com/package/@monordo/bitfield-permission-manager)




[0]: https://img.shields.io/badge/%20coverage%20-100-green?style=flat-square
[1]: https://img.shields.io/endpoint.svg?url=https%3A%2F%2Factions-badge.atrox.dev%2Fmonordo%2Fbitfield-permission-manager%2Fbadge%3Fref%3Dmain&style=flat-square

[2]: https://actions-badge.atrox.dev/monordo/bitfield-permission-manager/goto?ref=main
npm package: @monordo/json-vidal-client
Description: MonOrdo JSON Vidal client, based on the official Vidal API
Author: Cariz
Latest version: 0.0.1

# json-vidal-client
![MonOrdo logo](https://www.monordo.com/wp-content/uploads/2022/06/MonOrdo.jpg)
![Vidal group logo](https://encrypted-tbn0.gstatic.com/images?q=tbn:ANd9GcSRK7hPinOTbq0iswEaSAl6wofd3YTmRQyd78hcE_YPIWar32niDvwwnNURHAnb-Jn7LQ&usqp=CAU)

This library is developed and maintained by the MonOrdo development team. It aims to simplify the integration of the [Vidal API](https://www.vidalfrance.com/solutions/vidal-integrated) so that you can focus on the business.
It is developed in [Typescript](https://www.typescriptlang.org/branding/), and uses the [NestJs](https://nestjs.com/) injection system. The returned objects are typed and in [JSON](https://fr.wikipedia.org/wiki/JavaScript_Object_Notation).

For any problem with the library, you can open a ticket on GitHub. If you need an action on the API to be taken into account, you can also submit it on GitHub or propose a pull request if you made the changes directly on our repository

**Repository:** [https://github.com/monordo/json-vidal-client](https://github.com/monordo/json-vidal-client)

**Official documentation:** [https://monordo.gitbook.io/json-vidal-client/](https://monordo.gitbook.io/json-vidal-client/)

**Generated documentation (typedoc):** [https://monordo.github.io/json-vidal-client/](https://monordo.github.io/json-vidal-client/)

**NPM details:** [https://www.npmjs.com/package/@monordo/json-vidal-client](https://www.npmjs.com/package/@monordo/vidal-client)
npm package: @monoreact/package-example
Description: > This package meant for developing React components (not apps!) that can be published to NPM. If you’re looking to build an app, you should use `create-react-app`, `razzle`, `nextjs`, `gatsby`, or `react-static`.
Author: Maksym Tarsis
Latest version: 0.1.0

# User Guide

> This package meant for developing React components (not apps!) that can be published to NPM. If you’re looking to build an app, you should use `create-react-app`, `razzle`, `nextjs`, `gatsby`, or `react-static`.

> If you’re new to TypeScript and React, checkout [this handy cheatsheet](https://github.com/sw-yx/react-typescript-cheatsheet/)

## Commands

Monoreact scaffolds your new library inside `/src`, and also sets up a [Parcel-based](https://parceljs.org) playground for it inside `/example`.

```
yarn start
```

This builds to `/dist` and runs the project in watch mode so any edits you save inside `src` causes a rebuild to `/dist`.

Then run either example playground or storybook:

### Docz

Run inside another terminal:

```
yarn docz
```

This loads the component documentation of `*.mdx` extension.

### Example

Then run the example inside another:

```
cd example
yarn install
yarn start
```

The default example imports and live reloads whatever is in `/dist`, so if you are seeing an out of date component, make sure the package is running in watch mode.

To do a one-off build, use `yarn build`.

To run tests, use `yarn test`.

### Jest

Jest tests are set up to run with `yarn test`. This runs the test watcher (Jest) in an interactive mode. By default, runs tests related to files changed since the last commit.

### Rollup

The package uses [Rollup v1.x](https://rollupjs.org) as a bundler and generates multiple rollup configs for various module formats and build settings. See [Optimizations](#optimizations) for details.

### TypeScript

`tsconfig.json` is set up to interpret `dom` and `esnext` types, as well as `react` for `jsx`. Adjust according to your needs.


## Using the Playground

```
cd example
yarn install
yarn start
```

The default example imports and live reloads whatever is in `/dist`, so if you are seeing an out of date component, make sure the package is running in watch mode like we recommend above.

## Named Exports

Per Palmer Group guidelines, [always use named exports.](https://github.com/palmerhq/typescript#exports) Code split inside your React app instead of your React library.

## Including Styles

There are many ways to ship styles, including with CSS-in-JS. Configure how you like.

For vanilla CSS, you can include it at the root directory and add it to the `files` section in your `package.json`, so that it can be imported separately by your users and run through their bundler's loader.

## Publishing to NPM

We recommend using https://github.com/sindresorhus/np.
npm package: @monorepo-semantic-release/git
Description: semantic-release plugin to commit monorepo's release assets to the project's git repository
Author: twinh
Latest version: 1.3.0

# @monorepo-semantic-release/git

[**semantic-release**](https://github.com/semantic-release/semantic-release) plugin to commit monorepo's release assets to the project's [git](https://git-scm.com/) repository.
npm package: @monorepo-semantic-release/github
Description: semantic-release plugin for monorepo to publish a GitHub release and comment on released Pull Requests/Issues
Author: twinh
Latest version: 1.1.0

# @monorepo-semantic-release/github

[**semantic-release**](https://github.com/semantic-release/semantic-release) plugin for monorepo to publish a
[GitHub release](https://help.github.com/articles/about-releases) and comment on released Pull Requests/Issues.
npm package: @monorepo-semantic-release/monorepo
Description: [**semantic-release**](https://github.com/semantic-release/semantic-release) plugin to manage monorepo packages version and dependencies.
Author: twinh
Latest version: 2.2.2

# @monorepo-semantic-release/monorepo

[**semantic-release**](https://github.com/semantic-release/semantic-release) plugin to manage monorepo packages version and dependencies.
npm package: @monorepo-semantic-release/replace
Description: [**semantic-release**](https://github.com/semantic-release/semantic-release) plugin to replace file content in monorepo packages.
Author: twinh
Latest version: 1.1.0

# @monorepo-semantic-release/replace

[**semantic-release**](https://github.com/semantic-release/semantic-release) plugin to replace file content in monorepo packages.
npm package: @monorepo-semantic-release/zero-commit-analyzer
Description: [**semantic-release**](https://github.com/semantic-release/semantic-release) plugin to analyze commits for *zero* major version package with [conventional-changelog](https://github.com/conventional-changelog/conventional-changelog)
Author: twinh
Latest version: 1.0.2

# @monorepo-semantic-release/zero-commit-analyzer

[**semantic-release**](https://github.com/semantic-release/semantic-release) plugin to analyze commits for *zero* major version package with [conventional-changelog](https://github.com/conventional-changelog/conventional-changelog)
npm package: @monorepo-setup/pkg-utils
Description: comprehensive utility library for monorepo demonstration - includes TypeScript types, async utilities, validation, caching, event system, and performance monitoring
Author: sutie
Latest version: 0.0.1

# pkg-utils

一个全面的 TypeScript 工具库，专为 monorepo 项目设计，展示各种前端开发场景的最佳实践。

## 🚀 特性

### 📊 基础常量和配置
- **常量导出**: `one`, `two`
- **配置对象**: `CONFIG` - 包含 API URL、超时、版本等
- **枚举类型**: `Status`, `Priority` - 状态和优先级管理

### 🧩 TypeScript 类型定义
- **接口**: `User`, `Role`, `Permission` - 用户权限系统
- **泛型类型**: `ApiResponse<T>`, `AsyncResult<T>`, `EventHandler<T>`
- **工具类型**: `ValidatorRule<T>` - 验证规则配置

### 🛠️ 功能模块

- **数学工具** - 数值计算、范围限制、随机数生成
- **字符串工具** - 格式化、转换、截断处理
- **数组工具** - 去重、分组、分块操作
- **对象工具** - 深拷贝、属性选择、数据转换
- **异步工具** - 延迟、超时、重试、批量处理
- **数据验证** - 类型安全的验证框架
- **事件系统** - 类型安全的事件发射器
- **缓存系统** - LRU 缓存实现
- **错误处理** - 自定义错误类和安全包装
- **日期工具** - 格式化、计算、判断
- **性能监控** - 执行时间测量和指标收集

## 📦 安装和使用

```bash
# 在 monorepo 内使用
pnpm add pkg-utils@workspace:*
```

### 基本用法

```typescript
// 按需导入（推荐）
import { clamp, capitalize, unique } from 'pkg-utils'

// 模块化导入（最佳 tree-shaking）
import { clamp } from 'pkg-utils/math'
import { capitalize } from 'pkg-utils/string'
```

## 📋 文档和示例

- **[examples/](./examples/)** - 完整使用示例
- **[src/](./src/)** - 源码和 TypeScript 类型定义
- **[test/](./test/)** - 单元测试覆盖

## 🧪 开发

```bash
pnpm test              # 运行测试
pnpm build             # 构建发布版本
```
npm package: @monorepo-utilities/install-dependencies
Description: Builds node modules to a spectified path 📦
Author: yowainwright
Latest version: 1.3.0

# @monorepo-utilities/install-dependencies 🧱 📦

![Typed with TypeScript](https://flat.badgen.net/badge/icon/Typed?icon=typescript&label&labelColor=blue&color=555555)
[![npm version](https://badge.fury.io/js/%40monorepo-utilities%2Finstall-dependencies.svg)](https://www.npmjs.com/package/@monorepo-utilities/install-dependencies)

_Install Dependencies_ is CLI which helps you install monorepo package dependencies with control!

## Why tho?

When working in [monorepo workspaces](https://pnpm.io/workspaces), installing exact node modules within a package can be difficult! With `install-dependencies`, developers can enjoy [local package referencing](https://pnpm.io/workspaces#workspace-protocol-workspace) and **exact** node module installs!

---

## Install

```sh
pnpm install @monorepo-utilities/install-dependencies
```

## Usage

To use install-dependencies, simply run `install-deps`.

Or, if you need more control, use the options below!

```sh
Usage: install-deps [options]

Options:
  -V, --version          output the version number
  -c, --config <config>  config path
  --debug                enables debug mode
  -d, --dest <string>    dest path
  -f, --file <file>      path to package.json file
  --has-lockfile         use lock file
  --isTesting            enables testing, no scripts are run
  -p, --path <path>      path to package.json file
  -r, --runner <runner>  npm, pnpm, or yarn
  -h, --help             display help for command
```

---

### Optional Specificity

If you want even more control, you can add `installDependencies` or `ideps` object to your  package's `package.json`.
Now, you can optionally add packages to ignore using an `ignore` array or you can include more using `include` object!

```ts
"installDependencies": {
  "include": {
    "react": "17.0.1",
    "@babel/core": "7.12.10",
    "typescript": "4.1.2"
  },
  "ignore": [
    "ramda"
  ]
}
```

If you'd prefer this functionality without adding an object to your `package.json`, you can add it to an `.idepsrc` config

```ts
{
  "include": {
    "react": "17.0.1",
    "@babel/core": "7.12.10",
    "typescript": "4.1.2"
  },
  "ignore": [
    "ramda"
  ]
}
```

---

## Monorepo Utilities 🧱

**Utilities for monorepo development.**

Javascript utilities for better monorepo results.

---

View other [monorepo utilities](../../). Made by [@yowainwright](https://github.com/yowainwright) for fun with passion! MIT, 2022
npm package: @monorepo-utils/collect-changelog
Description: Collect CHANGELOG from tags.
Author: azu
Latest version: 2.11.0

# @monorepo-utils/collect-changelog

Collect CHANGELOG from tags.

## Feature

- Support independent mode
    - Currently it support [Independent mode](https://github.com/lerna/lerna#independent-mode---independent) only
- Get CHANGELOG from each package's `CHANGELOG.md`

## Install

Install with [npm](https://www.npmjs.com/):

    npm install @monorepo-utils/collect-changelog

## Usage

    Usage
      $ collect-changelog-from-tag [option] "tag@version"

    Options
      --changelog the file path of CHANGELOG.md
      --directory the root directory of monorepo
      --template  handlebars template path
      --name set package name if it not defined

    Examples
      $ collect-changelog-from-tag --directory /path/to/monorepo-project/ "tag@version"
      # current directory is project root for independent mode
      $ collect-changelog-from-tag "tag@version"
      # get changelog content from specific CHANGELOG.md for fixed mode
      $ collect-changelog-from-tag --changelog ./CHANGELOG.md "tag@version"
      

## Example

    $ monorepo-utils-collect-changelog "textlint@8.0.0"
    
    ## textlint@8.0.0
    
    ### fixes
    
    - **babel:** ignore lib directory ([12e581d](https://github.com/textlint/textlint/commit/12e581d))
    - **fixer:** fix thrown error when empty result. (#274) ([7013cee](https://github.com/textlint/textlint/commit/7013cee)), closes [#274](https://github.com/textlint/textlint/issues/274)
    - **textilnt:** fix JSDoc ([8a417e0](https://github.com/textlint/textlint/commit/8a417e0))
    
    ### features
    
    - **packages:** import textlint-plugin-text ([1b7a571](https://github.com/textlint/textlint/commit/1b7a571))
    - **textlint:** update built-in textlint-plugin-markdown@^2 (#282) ([448fef9](https://github.com/textlint/textlint/commit/448fef9))
    
    ### breakingChanges
    
    - **textlint:** markdown-to-ast@4 includes some breaking change

Get all changelog at point.

    $ lerna publish --skip-npm
    # tag each packages
    $ git tag --points-at HEAD | xargs -I{} monorepo-utils-collect-changelog {}
    # get CHANGELOG from each packages

## Author

- [github/azu](https://github.com/azu)
- [twitter/azu_re](https://twitter.com/azu_re)

## License

MIT © azu
npm package: @monorepo-utils/package-utils
Description: Package utility for monorepo.
Author: azu
Latest version: 2.11.0

# @monorepo-utils/package-utils

Package utility for monorepo.

## Install

Install with [npm](https://www.npmjs.com/):

    npm install @monorepo-utils/package-utils

## Usage

### `getPackages(rootDirectory: string): PackageResult[]`

```ts
export interface PackageResult {
    // path to package's directory
    location: string;
    // package.json content
    packageJSON: any;
}
export declare const getPackages: (rootDirectory: string) => PackageResult[];
```

## Changelog

See [Releases page](https://github.com/azu/monorepo-utils/releases).

## Running tests

    yarn test

## Contributing

Pull requests and stars are always welcome.

For bugs and feature requests, [please create an issue](https://github.com/azu/monorepo-utils/issues).

1. Fork it!
2. Create your feature branch: `git checkout -b my-new-feature`
3. Commit your changes: `git commit -am 'Add some feature'`
4. Push to the branch: `git push origin my-new-feature`
5. Submit a pull request :D

## Author

- [github/azu](https://github.com/azu)
- [twitter/azu_re](https://twitter.com/azu_re)

## License

MIT © azu

Thanks to [azz/get-monorepo-packages: Get a list of packages from a monorepo](https://github.com/azz/get-monorepo-packages)
npm package: @monorepo-utils/publish
Description: Publish packages to npm if needed. 
Latest version: 2.1.0
Deprecated: Use lerna version and lerna publish directory

# @monorepo-utils/publish

Publish packages to npm if needed. 

## Install
   
     npm install --save-dev @monorepo-utils/publish

## Usage

    Usage
      $ monorepo-utils-publish

    Options:
      --dry Enable dry run mode
      --yes Yes all
      --ci  CI mode includes --yes flag
      --dist-tag dist-tag for npm

    Examples
      # publish 
      $ monorepo-utils-publish --dry
      # publish with --tag
      # https://docs.npmjs.com/cli/publish
      $ monorepo-utils-publish --dist-tag next
      
      # dry-run mode
      $ monorepo-utils-publish --dry
      # manually publish
      # CI mode
      $ monorepo-utils-publish --ci


## Publish

Publish packages that are publish-able.

[can-npm-publish](https://github.com/azu/can-npm-publish) detect publish-able of the package.

**Dry-run**:

Test publishing with `--dry`

    $ monorepo-utils-publish --dry

Actual publishing:

    $ monorepo-utils-publish 

CI flag skip interactive mode.

    $ monorepo-utils-publish --ci

## UseCase

You can use this script for splitting tagging and publishing.

For example, [@lerna/publish](https://github.com/lerna/lerna/tree/master/commands/publish#readme) does tag and publish together.
You want to split that process into two phase.

1. Tagging(update version and git tag) 

```
$ lerna publish --skip-npm --conventional-commits
````

2. Publishing

```
monorepo-utils-publish
```
npm package: @monorepojs/renovate-config
Description: Preset monorepojs config for Renovate
Latest version: 0.1.4

# @monorepojs Renovate Preset

This directory contains the renovate config preset for the `@monorepojs` monorepo.

It can be used by appending `@monorepojs` to the `extends` option in your `renovate` config. For example:

```json
{
  "extends": ["config:base", "@monorepojs"]
}
```

This preset ensures that dependencies from the `@monorepojs` monorepo will be upgraded at the same time (in same branch/PR).
npm package: @monorepojs/scripts
Description: Configuration and scripts for MonorepoJS
Latest version: 0.9.1

# react-scripts fork

This is a copy of [react-scripts](https://github.com/facebook/create-react-app/tree/master/packages/react-scripts) with some bolted on monorepo support.

See https://monorepo-documentation.firebaseapp.com/docs/packages/monorepo-scripts/ for more information.