open-index/open-npm huggingface dataset:
npm package: @rtarik/spectralnn-paint-mixer
Description: JavaScript runtime package for SpectralNN Paint Mixer.
Latest version: 0.1.0-alpha.1

# SpectralNN Paint Mixer For JavaScript

JavaScript runtime package for paint-aware color mixing built on a subtractive physical base model plus learned residual correction.

Package name:

- `@rtarik/spectralnn-paint-mixer`

Repository:

- `https://github.com/rtarik/spectralnn-paint-mixer`

## Current Scope

- shared `SrgbColor` and `MixPortion` runtime types
- pipeline composition via `PipelinePaintMixer`
- the JavaScript port of the custom `spectral_ks_v1` base engine
- canonical model artifact loading
- learned residual correction inference against the bundled baseline artifact
- `PaintMixers.default()` for the full bundled baseline pipeline

The same package output is used by the landing page under `apps/site`, so browser-facing validation happens against the real package build rather than parallel demo-only logic.

## Install

After the alpha is published:

```bash
npm install @rtarik/spectralnn-paint-mixer@alpha
```

## Example

```js
import {
  MixPortion,
  PaintMixers,
  SrgbColor,
} from '@rtarik/spectralnn-paint-mixer';

const mixer = PaintMixers.default();

const result = mixer.mixOrNull([
  new MixPortion({ color: SrgbColor.fromHex('#E53935'), parts: 1 }),
  new MixPortion({ color: SrgbColor.fromHex('#283593'), parts: 1 }),
]);

console.log(result?.toHexString());
```

## Build

Build the package output consumed by the site and later npm publish flow:

```bash
npm run build
```

## Validation

Run the package tests:

```bash
npm test
```

From the repository root, validate the package through the landing page too:

```bash
node apps/site/scripts/smoke-site.mjs
```

## Notes

- `src/generated/default-model-artifact.json` is a bundled copy of the canonical artifact in `artifacts/model/baseline-v1/model.json`.
- `src/generated/default-model-artifact-data.js` is the browser-safe wrapper used by the runtime package.
- `dist/` is the publish-facing output used by both the landing-page build and the npm tarball.
- end-to-end parity runs against `artifacts/fixtures/baseline-v1/curated-parity.json`.
- residual-stage parity fixtures live in `artifacts/fixtures/baseline-v1/residual-parity.json`.
npm package: @rtarojs/mcp-rtaro-ui
Description: MCP UI builder by RTaro UI
Latest version: 1.0.1

# RTaro UI MCP

RTaro UI MCP 是一项独立的 MCP（模型上下文协议）服务，旨在将 RTaro UI 与大模型连接起来。它使大模型能够直接从文档中检索组件、API数据。

## 介绍

RTaro UI 是基于 Taro 框架的 React UI 组件库，提供丰富的移动端组件。

RTaro UI MCP 是一项独立的 MCP（模型上下文协议）服务，旨在将 RTaro UI 与大模型连接起来。它使大模型能够直接从文档中检索组件、API数据。

## 特点

- 🚀 直接使用 npx 运行，无需安装
- 📦 无需外部依赖，只需要 Node 环境
- 🔧 支持 Augment、Cursor 等主流AI工具
- 📋 包含81个RTaro UI组件的完整文档

## 使用方法

### Augment 用法

在Augment中使用RTaro UI MCP服务：

1. **打开Augment设置**
   - 点击设置图标或使用快捷键
   - 找到 "Model Context Protocol" 或 "MCP" 设置

2. **添加MCP服务器配置**
   ```json
   {
     "mcpServers": {
       "@rtarojs/mcp-rtaro-ui": {
         "command": "npx",
         "args": [
           "-y",
           "@rtarojs/mcp-rtaro-ui"
         ],
         "env": {}
       }
     }
   }
   ```

3. **重启Augment**
   - 保存配置后重启Augment以加载MCP服务

4. **开始使用**
   - 在对话中询问RTaro UI组件相关问题
   - AI会自动调用MCP工具获取组件信息

📖 **详细配置指南**: 查看 [AUGMENT.md](./AUGMENT.md) 获取完整的Augment配置和使用说明

### Cursor 用法

Cursor MCP 使用指南参考：[https://docs.cursor.com/context/model-context-protocol#using-mcp-tools-in-agent](https://docs.cursor.com/context/model-context-protocol#using-mcp-tools-in-agent)

```json
{
  "mcpServers": {
    "@rtarojs/mcp-rtaro-ui": {
      "command": "npx",
      "args": [
        "-y",
        "@rtarojs/mcp-rtaro-ui"
      ],
      "env": {}
    }
  }
}
```

## 功能特性

- 📋 列出所有可用的 RTaro UI 组件 (81个组件)
- 📖 获取组件的详细文档
- 🔧 获取组件的 API 参数说明
- 💡 获取组件的使用示例
- 🔍 根据关键词搜索组件
- 🚀 获取快速开始指南
- 📚 获取项目介绍文档

## 可用工具

### `list-components`
列出所有可用的 RTaro UI 组件

### `get-component-docs`
获取指定组件的详细文档
- 参数: `componentName` (string) - 组件名称，例如: button, input, modal 等

### `get-component-props`
获取指定组件的属性和API文档
- 参数: `componentName` (string) - 组件名称

### `get-component-examples`
获取指定组件的使用示例和代码
- 参数: `componentName` (string) - 组件名称

### `search-components`
根据关键词搜索相关组件
- 参数: `keyword` (string) - 搜索关键词，例如: 按钮, 输入, 表单 等

### `get-quick-start`
获取 RTaro UI 的快速开始指南

### `get-introduction`
获取 RTaro UI 的介绍文档

## 开发

```bash
# 安装依赖
npm install

# 开发模式
npm run dev

# 构建
npm run build

# 分析文档
npm run analyze

# 测试服务
npm test
```

## 发布前准备

在发布新版本前，请确保运行以下命令更新文档：

```bash
# 复制最新的组件文档到 metaData
npm run copy-docs

# 构建项目
npm run build

# 检查打包内容
npm pack --dry-run
```

### 自动化发布流程

项目配置了自动化的发布流程：

- `prebuild`: 构建前自动复制最新文档
- `prepublishOnly`: 发布前自动构建项目
- `files` 字段确保 metaData 目录被包含在发布包中

直接运行 `npm publish` 即可，无需手动执行其他命令。

## 项目结构

```
packages/rtaro-ui-mcp/
├── src/                    # 源代码
│   ├── index.ts           # 主入口文件
│   ├── services/          # 服务层
│   └── tools/             # MCP工具定义
├── scripts/               # 构建脚本
│   ├── copy-docs.ts      # 复制文档脚本
│   ├── analyze-doc.ts    # 分析文档脚本
│   └── test-service.ts   # 测试服务脚本
├── metaData/             # 文档数据
│   └── docs/             # 组件文档
│       ├── *.md          # 各组件文档
│       └── index.json    # 组件索引
└── dist/                 # 构建输出
```

## 注意事项

- metaData 目录包含了所有组件文档的副本，确保MCP服务不依赖外部文件
- 每次发布前需要运行 `npm run copy-docs` 来更新文档
- 构建过程会自动执行文档复制（通过 prebuild 钩子）

## License

MIT
npm package: @rtawebteam/n8n-nodes-zalo
Description: Custom n8n node to interact with Zalo OA APIs
Author: Cai Ngoc Anh Tai
Latest version: 1.0.3

# n8n-zalo

This is an n8n custom node for consuming the Zalo OA API. With this node, you can easily integrate Zalo into your n8n workflows and automate tasks such as sending messages, retrieving user information, and uploading files.

## Prerequisites
Before using this node, you'll need to obtain an app ID and OA access token from the Zalo Developer Platform. You can find more information on how to do this in the Zalo API documentation.

## Installation
Follow the [installation guide](https://docs.n8n.io/integrations/community-nodes/installation/) in the n8n community nodes documentation.
npm package: @rtbenfield/tsconfig-workers
Description: TSConfig bases for Cloudflare Workers
Author: Tyler Benfield
Latest version: 0.0.3

# TSConfig base for Cloudflare Workers

This packages provides a base TSConfig file for use within Cloudflare Workers projects. It's intended to complement the excellent [@tsconfig/bases](https://github.com/tsconfig/bases) project.

## Usage

Add the package to your `"devDependencies"`:

```sh
npm install --save-dev @rtbenfield/tsconfig-workers
```

Add to your `tsconfig.json`:

```json
"extends": "@rtbenfield/tsconfig-workers"
```

### Usage with @tsconfig/bases

It's recommended to use this base alongside [@tsconfig/strictest](https://www.npmjs.com/package/@tsconfig/strictest):

Add both packages to your `"devDependencies"`:

```sh
npm install --save-dev @rtbenfield/tsconfig-workers @tsconfig/strictest
```

Add to your `tsconfig.json`:

```json
"extends": ["@tsconfig/strictest", "@rtbenfield/tsconfig-workers"]
```
npm package: @rtbhouse/google-iap-auth
Description: Helper library to perfrorm requests to OIDC-authenticated resources (Cloud Identity-Aware Proxy)
Author: RTB House
Latest version: 0.1.2

# @rtbhouse/google-iap-auth

Helper library to perfrorm requests to OIDC-authenticated resources (Cloud Identity-Aware Proxy)

## Installation

```shell
npm install @rtbhouse/google-iap-auth
```

## Usage

To use this library you must have the following:

- Identity Aware Proxy protected resource
- Service account with permissions to read protected resource
- OAuth credentials with key file in JSON format (
  [more](https://cloud.google.com/iam/docs/creating-managing-service-account-keys#iam-service-account-keys-create-console)
  on generating Service Account json keys)

Example usage with [got](https://www.npmjs.com/package/got):

```typescript
import fs from 'fs';
import got from "got";
import { GoogleIapAuth } from "@rtbhouse/google-iap-auth";


const keyStr = fs.readFileSync('key.json', 'utf-8');
const keyData = JSON.parse(keyStr);
const googleIapAuth = new GoogleIapAuth("<oauth_client_id>", keyData);
const authorizedGot = got.extend({
  hooks: {
    beforeRequest: [
      async options => {
        options.headers.Authorization = `Bearer ${await googleIapAuth.getToken()}`;
      }
    ]
  },
  responseType: "json",
  followRedirect: false,
  mutableDefaults: true
});

(async () => {
  const response = await authorizedGot(
    "https://some.iap.protected.resource.com/"
  );
  console.log(response.statusCode);
  console.log(response.body);
})();
npm package: @rtbhouse/logger
Description: Logger inspired by python logging module with batch async API
Author: RTB House
Latest version: 0.3.2
Deprecated: this package has been deprecated

# @rtbhouse/logger

## Logger types

* `ConsoleLogger`: use window.console to log records
* `ObjectLogger`: return record e.g. render in DOM
* `ApiLogger`: send every log record to specific endpoint (`host` option)
* `ApiBatchLogger`: save records in local storage and sends them in batch to specific endpoint

## Usage:

```ts
import {ConsoleLogger, Level} from '@rtbhouse/logger';

const logger = new ConsoleLogger({level: Level.INFO});
logger.info('new user logged in', {id: user.id});
logger.warning('password expired', {date: user.lastChangeDate});
logger.error('error occured!', {error: err.toString()});
```