open-index/open-npm huggingface dataset:
npm package: @peartree/build
Description: Default description for build
Author: Matt Penrice
Latest version: 0.7.0

<p align="center">
  <a href="" rel="noopener">
 <img width=200px height=200px src="https://i.imgur.com/6wj0hh6.jpg" alt="Project logo"></a>
</p>

<h3 align="center">build</h3>

<div align="center">

[![Status](https://img.shields.io/badge/status-active-success.svg)]()
[![GitHub Issues](https://img.shields.io/github/issues/kylelobo/The-Documentation-Compendium.svg)](https://github.com/elmpp/peartree/issues)
[![GitHub Pull Requests](https://img.shields.io/github/issues-pr/kylelobo/The-Documentation-Compendium.svg)](https://github.com/elmpp/peartree/pulls)
[![License](https://img.shields.io/badge/license-MIT-blue.svg)](/LICENSE)

</div>

---


<p align="center"> Few lines describing your project.
    <br>
</p>

## 📝 Table of Contents

- [About](#about)
- [Getting Started](#getting_started)
- [Deployment](#deployment)
- [Usage](#usage)
- [Built Using](#built_using)
- [TODO](../TODO.md)
- [Contributing](../CONTRIBUTING.md)
- [Authors](#authors)
- [Acknowledgments](#acknowledgement)

## 🧐 About <a name = "about"></a>

Write about 1-2 paragraphs describing the purpose of your project.

## 🏁 Getting Started <a name = "getting_started"></a>

These instructions will get you a copy of the project up and running on your local machine for development and testing purposes. See [deployment](#deployment) for notes on how to deploy the project on a live system.

### Prerequisites

What things you need to install the software and how to install them.

```
Give examples
```

### Installing

A step by step series of examples that tell you how to get a development env running.

Say what the step will be

```
Give the example
```

And repeat

```
until finished
```

End with an example of getting some data out of the system or using it for a little demo.

## 🔧 Running the tests <a name = "tests"></a>

Explain how to run the automated tests for this system.

### Break down into end to end tests

Explain what these tests test and why

```
Give an example
```

### And coding style tests

Explain what these tests test and why

```
Give an example
```

## 🎈 Usage <a name="usage"></a>

Add notes about how to use the system.

## 🚀 Deployment <a name = "deployment"></a>

Add additional notes about how to deploy this on a live system.

## ⛏️ Built Using <a name = "built_using"></a>

- [MongoDB](https://www.mongodb.com/) - Database
- [Express](https://expressjs.com/) - Server Framework
- [VueJs](https://vuejs.org/) - Web Framework
- [NodeJs](https://nodejs.org/en/) - Server Environment

## ✍️ Authors <a name = "authors"></a>

- [@kylelobo](https://github.com/kylelobo) - Idea & Initial work

See also the list of [contributors](https://github.com/kylelobo/The-Documentation-Compendium/contributors) who participated in this project.

## 🎉 Acknowledgements <a name = "acknowledgement"></a>

- Hat tip to anyone whose code was used
- Inspiration
- References
npm package: @peartree/build-toolkit
Description: Default description for build
Author: Matt Penrice
Latest version: 0.7.2

# Build Toolkit

## Table of Contents
+ [Problem](#problem)
+ [Getting Started](#solution)
+ [Installation](#installation)
+ [Contributing](../CONTRIBUTING.md)

## The Problem <a name = "problem"></a>

Declarative configuration is great but the learning cost is high for the majority of folk. Sometimes
you just want to take a config and sprinkle on a few settings. This is especially true when
you may be using several bundlers for the same codebase (e.g. web/mobile)

## This Solution <a name = "solution"></a>

Bundler config util offers a grab bag of imperative "plugins" that understand the config
they're operating on. Just stack them up and get a perfect config out the other end

We have found for our projects this really helps with auditing what it is we want our
bundler to actually do for us. It's far too easy for codebases and bundler configs to get
out of sync


## Installation <a name = "installation"></a>

```bash
yarn add -D @peartree/webpack-config-util
```

```
// webpack.config.js
const {mainFields} = require('@peartree/webpack-config-util')

module.exports =
```

And repeat

```
until finished
```

End with an example of getting some data out of the system or using it for a little demo.
npm package: @pearzap/swap-sdk
Description: 🛠 An SDK for building applications on top of SushiSwap.
Latest version: 5.0.0-canary.201

# 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/pearzap/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/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: @peaske7/readit
Description: A CLI tool to review Markdown documents with inline comments
Author: Jay Shimada
Latest version: 0.2.0

# readit

A CLI tool to review Markdown and HTML documents with inline comments. Add margin notes to highlighted text, then export for AI or apply back to source.

<img width="4014" height="2440" alt="CleanShot 2025-12-25 at 09 23 20@2x" src="https://github.com/user-attachments/assets/2dfda51c-b5a2-45ef-839f-e3ab5854bf90" />

![CleanShot 2025-12-25 at 09 28 39](https://github.com/user-attachments/assets/f111da46-da64-4193-a2d5-49310ef9d060)

Inspired by [difit](https://github.com/yoshiko-pg/difit).

## Requirements

- [Bun](https://bun.sh) >= 1.0

## Quick Start

```bash
bunx readit document.md
```

## Usage

```bash
readit <file>                 # Review a .md or .html file
readit <file> --port 3000     # Custom port (default: 4567)
readit <file> --host 0.0.0.0  # Custom host (default: 127.0.0.1)
readit <file> --no-open       # Don't auto-open browser
readit <file> --clean         # Clear existing comments

readit list                  # List all files with comments
readit show <file>           # Show comments for a file
```

Select text to add comments. Comments appear as margin notes. Copy all comments formatted for AI with a single click.

## Development

```bash
bun install       # Install dependencies
bun dev           # Start dev server
bun run build     # Build for production
bun run test      # Run tests
bun run check     # Lint and format (Biome)
```

## License

MIT