open-index/open-npm huggingface dataset:
npm package: @ignitefi/sdk
Description: 🛠 An SDK for building applications on top of Ignite Finance.
Latest version: 0.0.30

# Uniswap SDK

[![code style: prettier](https://img.shields.io/badge/code_style-prettier-ff69b4.svg?style=flat-square)](https://github.com/prettier/prettier)
[![Actions Status](https://github.com/Uniswap/uniswap-sdk/workflows/CI/badge.svg)](https://github.com/Uniswap/uniswap-sdk)
[![npm version](https://img.shields.io/npm/v/@uniswap/sdk/latest.svg)](https://www.npmjs.com/package/@uniswap/sdk/v/latest)
[![npm bundle size (scoped version)](https://img.shields.io/bundlephobia/minzip/@uniswap/sdk/latest.svg)](https://bundlephobia.com/result?p=@uniswap/sdk@latest)

In-depth documentation on this SDK is available at [uniswap.org](https://uniswap.org/docs/v2/SDK/getting-started/).

## 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/Uniswap/uniswap-sdk.git
```

Move into the uniswap-sdk working directory

```sh
cd uniswap-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: @ignitefixyz/sdk
Description: 🛠 An SDK for building applications on top of Ignite Finance.
Latest version: 0.0.25

# Uniswap SDK

[![code style: prettier](https://img.shields.io/badge/code_style-prettier-ff69b4.svg?style=flat-square)](https://github.com/prettier/prettier)
[![Actions Status](https://github.com/Uniswap/uniswap-sdk/workflows/CI/badge.svg)](https://github.com/Uniswap/uniswap-sdk)
[![npm version](https://img.shields.io/npm/v/@uniswap/sdk/latest.svg)](https://www.npmjs.com/package/@uniswap/sdk/v/latest)
[![npm bundle size (scoped version)](https://img.shields.io/bundlephobia/minzip/@uniswap/sdk/latest.svg)](https://bundlephobia.com/result?p=@uniswap/sdk@latest)

In-depth documentation on this SDK is available at [uniswap.org](https://uniswap.org/docs/v2/SDK/getting-started/).

## 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/Uniswap/uniswap-sdk.git
```

Move into the uniswap-sdk working directory

```sh
cd uniswap-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: @igniter-js/common
Description: Shared primitives for Igniter.js packages
Author: Felipe Barcelos
Latest version: 0.1.0

# @igniter-js/common

Shared primitives for Igniter.js packages.

## Contents

- `IgniterError`
- `IgniterLogger` types
- `StandardSchemaV1` types

## Usage

```ts
import { IgniterError, type IgniterLogger, type StandardSchemaV1 } from "@igniter-js/common";
```
npm package: @igniter-js/eslint
Description: ESLint configuration for Igniter.js projects.
Author: Felipe Barcelos
Latest version: 0.2.1

# @igniter-js/eslint-config

[![npm version](https://badge.fury.io/js/@igniter-js%2Feslint-config.svg)](https://www.npmjs.com/package/@igniter-js/eslint-config)
[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)

A carefully crafted ESLint and Prettier configuration preset for modern JavaScript and TypeScript projects. Enforce consistent code style and catch potential errors before they make it to production.

## Features

- 🎯 Optimized for TypeScript and JavaScript
- ⚡ Works seamlessly with Prettier
- 🔧 Zero configuration needed
- 📦 Easy to extend and customize

## Installation & Usage

### React (with Next.js)
Install dependencies:

```bash
npm i -D eslint @igniter-js/eslint-config
```

Inside `.eslintrc.json`:
```json
{
  "extends": [
    "@igniter-js/eslint-config/next",
    "next/core-web-vitals"
  ]
}
```

### React (without Next.js)
Install dependencies:

```bash
npm i -D eslint @igniter-js/eslint-config
```

Inside `.eslintrc.json`:
```json
{
  "extends": "@igniter-js/eslint-config/react"
}
```

### Node.js
Install dependencies:

```bash
npm i -D eslint @igniter-js/eslint-config
```

Inside `.eslintrc.json`:
```json
{
  "extends": "@igniter-js/eslint-config/node"
}
```

### With Prettier

This config includes Prettier settings. Add a `prettier.config.js` to your project:

```javascript
module.exports = require('@igniter-js/eslint-config/prettier')
```

## What's Included

This configuration includes settings for:

- ESLint recommended rules
- TypeScript ESLint rules
- React and JSX/TSX support
- Import/Export rules
- Prettier integration

## Customization

You can override any rules by adding them to your ESLint config file:

```json
{
  "extends": "@igniter-js/eslint-config",
  "rules": {
    // Your custom rules here
  }
}
```

## Contributing

1. Fork the repository
2. Create your feature branch (`git checkout -b feature/amazing-feature`)
3. Commit your changes (`git commit -m 'Add some amazing feature'`)
4. Push to the branch (`git push origin feature/amazing-feature`)
5. Open a Pull Request

## License

MIT License - see the [LICENSE](LICENSE) file for details

## Support

- 📝 [Documentation](https://github.com/felipebarcelospro/igniter-eslint-config)
- 🐛 [Issue Tracker](https://github.com/felipebarcelospro/igniter-eslint-config/issues)
- 💬 [Discussions](https://github.com/felipebarcelospro/igniter-eslint-config/discussions)

---

Made with ❤️ by Felipe Barcelos
npm package: @igniter-js/eslint-config
Description: ESLint configuration for Igniter Projects.
Author: Felipe Barcelos
Latest version: 0.1.0

# @igniter/eslint-config

[![npm version](https://badge.fury.io/js/@igniter%2Feslint-config.svg)](https://www.npmjs.com/package/@igniter/eslint-config)
[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)

A carefully crafted ESLint and Prettier configuration preset for modern JavaScript and TypeScript projects. Enforce consistent code style and catch potential errors before they make it to production.

## Features

- 🎯 Optimized for TypeScript and JavaScript
- ⚡ Works seamlessly with Prettier
- 🔧 Zero configuration needed
- 📦 Easy to extend and customize

## Installation

```bash
# Using npm
npm install --save-dev @igniter/eslint-config

# Using yarn
yarn add -D @igniter/eslint-config

# Using pnpm
pnpm add -D @igniter/eslint-config
```

## Usage

Add the following to your `.eslintrc.json` (or `.eslintrc.js`):

```json
{
  "extends": "@igniter/eslint-config"
}
```

### With Prettier

This config includes Prettier settings. Add a `prettier.config.js` to your project:

```javascript
module.exports = require('@igniter/eslint-config/prettier')
```

## What's Included

This configuration includes settings for:

- ESLint recommended rules
- TypeScript ESLint rules
- React and JSX/TSX support
- Import/Export rules
- Prettier integration

## Customization

You can override any rules by adding them to your ESLint config file:

```json
{
  "extends": "@igniter/eslint-config",
  "rules": {
    // Your custom rules here
  }
}
```

## Contributing

1. Fork the repository
2. Create your feature branch (`git checkout -b feature/amazing-feature`)
3. Commit your changes (`git commit -m 'Add some amazing feature'`)
4. Push to the branch (`git push origin feature/amazing-feature`)
5. Open a Pull Request

## License

MIT License - see the [LICENSE](LICENSE) file for details

## Support

- 📝 [Documentation](https://github.com/felipebarcelospro/igniter-eslint-config)
- 🐛 [Issue Tracker](https://github.com/felipebarcelospro/igniter-eslint-config/issues)
- 💬 [Discussions](https://github.com/felipebarcelospro/igniter-eslint-config/discussions)

---

Made with ❤️ by Felipe Barcelos
npm package: @igniter-js/plugin-better-auth
Description: Igniter.js plugin that wires BetterAuth API into an 'auth' controller automatically.
Latest version: 0.0.3

# @igniter-js/plugin-better-auth

Type-safe Igniter.js plugin that wires BetterAuth's `api` surface into an `auth` controller automatically.

Status: scaffold. It creates an `auth` controller and dynamically maps methods discovered under `auth.api` into Igniter actions. The mapping is conservative and can be refined once the exact BetterAuth API shape is confirmed.

## Install

```
npm i @igniter-js/plugin-better-auth better-auth
```

Peer dependency `@igniter-js/core` must be available in your workspace.

## Quick Start

```ts
import { Igniter } from '@igniter-js/core'
import { createBetterAuthPlugin } from '@igniter-js/plugin-better-auth'
import { betterAuth } from 'better-auth'

const auth = betterAuth({ /* your config */ })
const { plugin, controllers } = createBetterAuthPlugin(auth)

// Attach the plugin and auto-register the typed `auth` controller
const igniter = Igniter
  .addPlugin('betterAuth', plugin, controllers)
  .create()

// Merge with your own controllers as usual
const router = igniter.router({
  controllers: {
    // ...your controllers
  }
})

// Typed DX: router.caller.auth.<action>()
// Action names come from `auth.api`:
// - Direct functions → <key> (POST)
// - Method groups { get, post, ... } → <key>_get | <key>_post | ...
```

## Configuration

```ts
createBetterAuthPlugin({
  auth,                 // required BetterAuth instance
  controllerName: 'auth',
  pluginName: 'better-auth'
})
```

## How Mapping Works

- It inspects top-level keys under `auth.api`.
- If it finds REST-like method containers (e.g. `{ get, post, put, delete, patch }`), it creates an action per method: `<key>_get`, `<key>_post`, ...
- If it finds a function, it creates a `POST` action named `<key>`.
- Action path is `/<key>` inside the `auth` controller, so HTTP endpoints look like `/api/v1/auth/<key>`.

Notes:
- Input types are inferred from the function signature and wired to the Igniter action `$Input` via a virtual schema.
- You can refine/extend mapping or schemas later without changing your Igniter app code.

## License

MIT
npm package: @ignitetech/g2-mcp
Description: Smart local MCP proxy for G2 -- forwards doc/search tools to hosted server, executes export tools locally
Latest version: 0.2.0

# @ignitetech/g2-mcp

AI-powered copilot for Gensym G2. Provides 25+ tools for searching G2 documentation, analyzing knowledge bases, generating G2 code, and exporting KB contents — all accessible from your AI coding assistant.

## Prerequisites

- **Node.js 18+**
- **G2 installation** (required only for KB export — documentation and search tools work without G2)
- **API key** provided by your administrator

## Setup

Add the following to your MCP client configuration (Cursor, Claude Desktop, Windsurf, etc.):

```json
{
  "mcpServers": {
    "g2-mcp": {
      "command": "npx",
      "args": [
        "@ignitetech/g2-mcp",
        "https://g2mcp.ignitetech.ai/mcp/",
        "--header",
        "X-API-KEY:${G2_MCP_API_KEY}"
      ],
      "env": {
        "G2_MCP_API_KEY": "<your-api-key>",
        "G2_ROOT": "C:\\g2-2023-64\\g2"
      }
    }
  }
}
```

If you only need documentation and search tools (no KB export), you can omit `G2_ROOT`:

```json
{
  "mcpServers": {
    "g2-mcp": {
      "command": "npx",
      "args": [
        "@ignitetech/g2-mcp",
        "https://g2mcp.ignitetech.ai/mcp/",
        "--header",
        "X-API-KEY:${G2_MCP_API_KEY}"
      ],
      "env": {
        "G2_MCP_API_KEY": "<your-api-key>"
      }
    }
  }
}
```

## Environment Variables

| Variable | Required | Description |
|----------|----------|-------------|
| `G2_MCP_API_KEY` | Yes | API key for the G2 MCP server |
| `G2_ROOT` | For KB export | Path to your G2 installation directory (e.g., `C:\g2-2023-64\g2` or `/opt/g2/g2`) |

## What You Can Do

Once configured, ask your AI assistant to:

- **Search documentation** — "How do I create a rule in G2?"
- **Generate G2 code** — "Write a procedure that calculates average temperature"
- **Analyze your KB** — "Show me a summary of my knowledge base"
- **Find dependencies** — "What procedures does calculate-flow call?"
- **Export a KB** — "Export the g2-copilot knowledge base"

## Troubleshooting

**Tools not loading**
Verify your API key is correct and that the server URL in your config is reachable.

**KB export not working**
Ensure `G2_ROOT` points to your G2 installation directory and that the target KB path is correct.

## Support

Contact your Gensym administrator for API keys and support.
npm package: @igniteui-angular/schematics
Description: Ignite UI for Angular Schematics for ng new and ng generate
Latest version: 1.0.0-beta.4

# Getting Started With Schematics

This repository is a basic Schematic implementation that serves as a starting point to create and publish Schematics to NPM.

### Testing

To test locally, install `@angular-devkit/schematics-cli` globally and use the `schematics` command line tool. That tool acts the same as the `generate` command of the Angular CLI, but also has a debug mode.

Check the documentation with
```bash
schematics --help
```

### Unit Testing

`npm run test` will run the unit tests, using Jasmine as a runner and test framework.

### Publishing

To publish, simply do:

```bash
npm run build
npm publish
```

That's it!
npm package: @igniteuistudying/docs
Description: This template provides a minimal setup to get React working in Vite with HMR and some ESLint rules.
Latest version: 1.0.0

# React + TypeScript + Vite

This template provides a minimal setup to get React working in Vite with HMR and some ESLint rules.

Currently, two official plugins are available:

- [@vitejs/plugin-react](https://github.com/vitejs/vite-plugin-react/blob/main/packages/plugin-react/README.md) uses [Babel](https://babeljs.io/) for Fast Refresh
- [@vitejs/plugin-react-swc](https://github.com/vitejs/vite-plugin-react-swc) uses [SWC](https://swc.rs/) for Fast Refresh

## Expanding the ESLint configuration

If you are developing a production application, we recommend updating the configuration to enable type aware lint rules:

- Configure the top-level `parserOptions` property like this:

```js
export default tseslint.config({
  languageOptions: {
    // other options...
    parserOptions: {
      project: ['./tsconfig.node.json', './tsconfig.app.json'],
      tsconfigRootDir: import.meta.dirname,
    },
  },
})
```

- Replace `tseslint.configs.recommended` to `tseslint.configs.recommendedTypeChecked` or `tseslint.configs.strictTypeChecked`
- Optionally add `...tseslint.configs.stylisticTypeChecked`
- Install [eslint-plugin-react](https://github.com/jsx-eslint/eslint-plugin-react) and update the config:

```js
// eslint.config.js
import react from 'eslint-plugin-react'

export default tseslint.config({
  // Set the react version
  settings: { react: { version: '18.3' } },
  plugins: {
    // Add the react plugin
    react,
  },
  rules: {
    // other rules...
    // Enable its recommended rules
    ...react.configs.recommended.rules,
    ...react.configs['jsx-runtime'].rules,
  },
})
```