open-index/open-npm huggingface dataset:
npm package: @lb-xyz/sdk
Description: 🛠 An SDK for building applications on top of Trader Joe.
Latest version: 5.0.14

# Trader Joe SDK

This repo contains tools for developing with [TraderJoe XYZ](https://www.traderjoexyz.com) v1.

## Running

This project uses standard npm and yarn workflows.

Install dependencies

```sh
pnpm install
```

Compile

```sh
pnpm build
```

## Installation

This project is available as an npm package. Add to your project with `npm install @lb-xyz/sdk`

## Attribution

This code was adapted from this Uniswap repo: [uniswap-sdk](https://github.com/Uniswap/sdk).
npm package: @lb-xyz/sdk-core
Description: This repo contains tools for developing with [TraderJoe XYZ](https://www.traderjoexyz.com).
Latest version: 2.0.13

# Trader Joe core SDK

This repo contains tools for developing with [TraderJoe XYZ](https://www.traderjoexyz.com).

## Running

This project uses standard npm and yarn workflows.

Install dependencies

```sh
pnpm install
```

Compile

```sh
pnpm build
```

## Installation

This project is available as an npm package. Add to your project with `npm install @lb-xyz/sdk-core`

## Attribution

This code was adapted from this Uniswap repo: [uniswap-sdk](https://github.com/Uniswap/sdk).
npm package: @lb-xyz/sdk-v2
Description: This SDK contains tools for developing for the [Joe V2](https://www.traderjoexyz.com) protocol, which utilizes the Liquidity Book architecture.
Latest version: 3.0.28

# Joe V2 SDK

This SDK contains tools for developing for the [Joe V2](https://www.traderjoexyz.com) protocol, which utilizes the Liquidity Book architecture.

For more details:

- [Whitepaper](https://github.com/traderjoe-xyz/research/blob/main/JOE%20v2%20-%20Liquidity%20Book.pdf)
- [Developer Docs](https://docs.traderjoexyz.com/)
npm package: @lbagic/scaffold
Description: Scaffolding tool for official and custom starter templates and installations.
Latest version: 0.3.7

# What would you like to scaffold today?

Scaffolding tool for official and custom starter templates and installations.

- reactjs template (custom)
- vite
- astro
- eslint
- nestjs
- nextjs
etc...

```sh
npx @lbagic/scaffold@latest
```

<img src="https://raw.githubusercontent.com/lbagic/scaffold/main/media/example.JPG" style="max-width: 650px" width="100%" height="100%" />
npm package: @lbajsarowicz/warden-skill
Description: Agent Skill for Warden Docker development environments
Author: Lukasz Bajsarowicz
Latest version: 1.2.0

# Warden Agent Skill

Agent Skill for [Warden](https://warden.dev) – a Docker-based local development environment wrapper for PHP applications (Magento, Laravel, Symfony, WordPress, Drupal, and more).

## Installation

```bash
# Via skills CLI
npx skills add lbajsarowicz/ai-skills-warden

# Or via npm
npm install @lbajsarowicz/warden-skill
```

## What This Skill Provides

Teaches AI agents how to:

- Initialize and manage Warden environments
- Import/export databases (including `pv | gzip -d | warden db import` pattern)
- Run shell commands, debugging (Xdebug), and profiling (Blackfire, SPX)
- Manage global services (Traefik, DNS, Mailpit)
- Troubleshoot common issues (DNS, SSL, Xdebug, sync)
- Map `.env` variables to services and generate configuration tables

## Quick Reference

| Task | Command |
|------|---------|
| Start environment | `warden svc up -d && warden env up -d` |
| Database import | `pv dump.sql.gz \| gzip -d \| warden db import` |
| Interactive MySQL | `warden db connect` |
| Shell (debugging) | `warden debug` |
| Shell (normal) | `warden shell` |
| Preview config | `warden env config` |

## Links

- [Warden Documentation](https://docs.warden.dev)
- [Warden GitHub](https://github.com/wardenenv/warden)

## Publishing (Maintainers)

Releases are automated via Conventional Commits. Merge a PR with `feat:` or `fix:` commits to trigger a new version and npm publish.

### One-time Setup

1. **npm access token**
   - Create at https://www.npmjs.com/settings/lbajsarowicz/tokens
   - Type: Automation, enable "Bypass two-factor authentication (2FA)"
   - Add as GitHub secret: `NPM_TOKEN`

2. **GitHub PAT for release**
   - Create a Personal Access Token (classic: `repo` scope, or fine-grained: `Contents` + `Metadata` = Read and write)
   - Add as GitHub secret: `RELEASE_TOKEN`
   - **Branch protection**: If `main` is protected, add the PAT owner (e.g. `lbajsarowicz`) to **Settings → Branches → main → Allow specified actors to bypass required pull requests**. Otherwise the workflow's direct push will be rejected.

### Release Flow

1. Commit with Conventional Commits: `feat(commands): add X`, `fix(troubleshooting): correct Y`
2. Open PR and merge to `main`
3. CI calculates version, pushes version bump to `main`, creates tag (e.g. `v1.1.0`)
4. Release workflow publishes to npm and creates GitHub Release

## License

MIT
npm package: @lbatchelor/netlify-cli
Description: Netlify builds, deploys and hosts your front-end straight from Github.
Author: Netlify
Latest version: 1.2.2-patched.9

# Netlify CLI

The Netlify CLI tools lets you create, deploy, and delete new sites straight from your terminal.

---

# Why does this fork exist?

This fork exists due to errors we are getting when using the normal client. Some times the permalink
we get back doesn't actually work. This fork simply fetches that url a second time to ensure that
we are logging the correct one.

It also adds the ability to set a `WRITE_PERMALINK_TO_FILE` environment variable to write the url
to a file as well.

```
WRITE_PERMALINK_TO_FILE="permalink.txt" yarn netlify-patched -t $NETLIFY_TOKEN deploy --site-id $NETLIFY_SITE_ID_STAGING -p dist.zip
```

---

## Installation

To install the CLI tools:

```bash
npm install netlify-cli -g
```

## Usage

Deploy a front-end project that lives in `my-project` and builds to `dist` directory:

```bash
cd my-project/
netlify deploy dist
```

## Configuration and Authentication

The first time you use the netlify cli command you'll be asked to authenticate.

Your access token is stored in `~/.netlify/config`.

Netlify also stores a local `.netlify` file in the folder where you run `netlify deploy` from where the `site_id` is stored.

## Environments

You can easily setup different environments like `staging` or `production`. Just use the `-e` flag:

```bash
netlify deploy dist -e production
```

Netlify creates different sites with each their own URL for each of your environments and keeps track of them in the `.netlify` config file.

## Caveats

- netlify-cli is known to hang with an "ECONNRESET" error (parsed as JSON, it will look odd) when used from many CI environments.  This is a known issue that is only fixed in our alternate and current CLI:  https://github.com/netlify/netlifyctl

- netlify-cli is known to hang when used with Node.js version 8.1.0.  Version 8.1.2 works well