open-index/open-npm huggingface dataset:
npm package: @jpr-mystery/haigen-chat
Description: Biblioteca de componentes React multiplataforma
Author: Jean Reis
Latest version: 0.1.6

# Haigen Chat

Biblioteca de componentes React multiplataforma para web e React Native.

## Instalação

```bash
npm install @jpr-mystery/haigen-chat
# ou
yarn add @jpr-mystery/haigen-chat
```

## Uso

### Web (React)

```tsx
import { ButtonWeb } from '@jpr-mystery/haigen-chat/web';

function App() {
  return <ButtonWeb>Clique aqui</ButtonWeb>;
}
```

### React Native

```tsx
import { ButtonNative } from '@jpr-mystery/haigen-chat/rn';

function App() {
  return <ButtonNative>Clique aqui</ButtonNative>;
}
```

## Desenvolvimento

1. Clone o repositório
2. Instale as dependências:
```bash
npm install
```

3. Para desenvolvimento:
```bash
npm run dev
```

4. Para build:
```bash
npm run build
```

## Estrutura do Projeto

```
src
|-- core (lógica e código compartilhado)
    |-- types
    |-- hooks
    |-- utils
    |-- store
|-- web (componentes web)
|-- native (componentes React Native)
```

## Dependências

- React >= 16.8.0
- React DOM >= 16.8.0 (para web)
- React Native >= 0.60.0 (para mobile)

## Licença

MIT

## Autor

Jean Reis
npm package: @jpraneeth/auth-service-sdk
Description: Developer SDK for Auth Service scoped user APIs
Latest version: 0.1.2

# `@jpraneeth/auth-service-sdk`

Official JavaScript/TypeScript SDK for your Auth Service.

## Install

```bash
npm i @jpraneeth/auth-service-sdk
```

## Configure

Use environment variables:

```bash
AUTH_SERVICE_BASE_URL=https://praneeth-authentication.up.railway.app
AUTH_SERVICE_API_KEY=sk_live_xxx
AUTH_SERVICE_ACCESS_TOKEN=dev_at_xxx
```

Or pass values directly in code.

## Usage

```ts
import { AuthServiceClient } from "@jpraneeth/auth-service-sdk";

const client = new AuthServiceClient({
  baseUrl: process.env.AUTH_SERVICE_BASE_URL,
  apiKey: process.env.AUTH_SERVICE_API_KEY,
  accessToken: process.env.AUTH_SERVICE_ACCESS_TOKEN,
});

const created = await client.createUser({
  email: "alice@example.com",
  password: "strong-password",
  name: "Alice",
});

const users = await client.listUsers();
```

## Methods

- `listUsers()`
- `getUser(id)`
- `createUser({ email, password, name? })`
- `updateUser(id, { name?, isActive? })`
- `deleteUser(id)`

All calls automatically send:

- `x-api-key`
- `x-access-token`

## Publishing to npm

Do **not** run `npm publish` from the monorepo root (`auth-tutorial` is `"private": true` and npm will error with `EPRIVATE`).

From the repository root:

```bash
npm run sdk:publish
```

Do **not** use `npm publish --prefix packages/...` — in many npm versions that still publishes the **root** `package.json` (`auth-tutorial`), which is `private` and fails with `EPRIVATE`. Use the path form instead:

```bash
npm publish ./packages/auth-service-sdk --access public
```

Or from this folder only:

```bash
cd packages/auth-service-sdk
npm run build
npm publish --access public
```

Scoped packages use `publishConfig.access: "public"` so they stay free to install. The npm scope must be one you control (this package uses your username). To publish as `@auth-service/...`, create or join the `auth-service` org on npm and update the `name` in `package.json`.
npm package: @jprochazk/cbor
Description: Partial implementation of RFC 7049 (CBOR)
Author: Jan Procházka
Latest version: 0.5.0

[![Build Status](https://travis-ci.com/jprochazk/cbor.svg?branch=master)](https://travis-ci.com/jprochazk/cbor)
[![David](https://img.shields.io/david/dev/jprochazk/cbor)](https://github.com/jprochazk/cbor/blob/master/package.json)
[![GitHub](https://img.shields.io/github/license/jprochazk/cbor)](https://github.com/jprochazk/cbor/blob/master/LICENSE)

TypeScript implementation of the Concise Binary Object Representation [RFC 7049](https://tools.ietf.org/html/rfc7049). From the [official website](http://cbor.io/):

CBOR is a data format whose design goals include the possibility of extremely small code size, fairly small message size, and extensibility without the need for version negotiation.

The API is self-explanatory:
```js
// Initialize some data
const json = {
    "key": "value",
    "another key": [
        1, 2, 3
    ],
    "number": 3.141592653589793
    "nulls are also encoded": null
};

const encoded = CBOR.encode(json); // ArrayBuffer
const decoded = CBOR.decode(encoded); // Object

// You can also encode into a pre-allocated buffer
const encoded = CBOR.encodeInto(new ArrayBuffer(4096), data);
```

### Usage

The library is targeted for both Node and Browsers using NPM:
```
> npm install cbor@npm:jprochazk/cbor
```
This installs the library under the `cbor` alias.

```js
// as CommonJS
const CBOR = require("cbor");

// as an ES module
import CBOR from "cbor";

CBOR.encode(...);
CBOR.decode(...);
```

Or included in the page as a static script from the `unkpg` CDN:

```html
<script src="https://unpkg.com/@jprochazk/cbor@0.4.6"></script>
<script>
    // after including the script in the page, the CBOR object is available globally
    CBOR.encode(...);
    CBOR.decode(...);
</script>
```

### Benchmarks

Benchmark is available [here](https://jsbench.me/krkdop8101/1).

| Browser | CBOR.decode | CBOR.encode | CBOR.encodeInto |
| :------ | :---------- | :---------- | :-------------- |
| Chrome  | 5225 ops/s  | 8998 ops/s  | 9268 ops/s      |
| Firefox | 20454 ops/s | 22323 ops/s | 22900 ops/s     |

Results are on a i5-8600k intel processor. Your mileage may vary. The JSON data used in the test is 2 KB decoded and 1.8 KB encoded. I specifically chose this data, because it encodes badly (lots of nested objects with only a single property). The benchmark suggests the library can encode/decode around 10 MB/s in Chrome and around 50 MB/s in Firefox. Hopefully, these are meaningful results.

### Notes

There are a few things from the specification which are currently unimplemented:

-   Tags, and the items they represent:
    -   date/time, bignum/bigfloat as byte string, and others
-   16-bit float (IEEE754 binary16)
-   Integers larger than 32 bit (BigInt)

If you need one or more of these features, submit an [issue](https://github.com/jprochazk/cbor/issues).
npm package: @jprochazk/svelte-material-icons
Description: Wrapper over the [MaterialDesign](https://github.com/Templarian/MaterialDesign) repository which transforms all `.svg` files to `.svelte` components.
Latest version: 0.1.0

# svelte-material-icons

Wrapper over the [MaterialDesign](https://github.com/Templarian/MaterialDesign) repository which transforms all `.svg` files to `.svelte` components.

File names are converted from `kebab-case.svg` to `PascalCase.svelte`, e.g. `google-translate.svg` to `GoogleTranslate.svelte`. Each file is self-contained, so the package is easily tree-shakeable.

### Installation

To install `@jprochazk/svelte-material-icons` under the `material-icons` alias:

With `npm`:
```
$ npm install material-icons@npm:jprochazk/svelte-material-icons
```
With `yarn`:
```
$ yarn add material-icons@npm:@jprochazk/svelte-material-icons
```
Or manually add this to your `package.json` `dependencies`:
```
"material-icons": "npm:@jprochazk/svelte-material-icons"
```
And run `npm install` or `yarn install`.

### Usage

Search for icons at https://materialdesignicons.com/, then use them like so:

```html
<script>
  // google-translate.svg
  import GoogleTranslateIcon from "material-icons/GoogleTranslate.svelte";
</script>

<a target="_blank" rel="noopener noreferrer" href="https://translate.google.com/">
  <GoogleTranslateIcon />
</a>
```

Every component follows this template:
```html
<svg
  xmlns="http://www.w3.org/2000/svg"
  xmlns:xlink="http://www.w3.org/1999/xlink"
  version="1.1"
  width="24"
  height="24"
  viewBox="0 0 24 24"
  {...$$props}
>
  <path d="..." />
</svg>
```
`{...$$props}` allows you to overwrite/add any props, such as `width`, `height`, `class`, `on:click`, etc.:
```html
<script>
  import TranslateIcon from "material-icons/GoogleTranslate.svelte";
</script>

<TranslateIcon width="64" height="64" />
```
npm package: @jproto/perform-node
Description: Welcome to Jumio's official Node.js SDK for performing verifications with the [Perform Netverify API.](https://github.com/Jumio/implementation-guides/blob/master/netverify/performNetverify.md)
Latest version: 0.0.3

# Jumio Perform API Node.js SDK

Welcome to Jumio's official Node.js SDK for performing verifications with the [Perform Netverify API.](https://github.com/Jumio/implementation-guides/blob/master/netverify/performNetverify.md)

## Installation

The SDK can be added to your Node.js project using either

    yarn add @jdemo/perform-node

or

    npm i @jdemo/perform-node

## Example Integration

An example integration can be found at the [Perform Node Repo.](https://github.com/Jumio/perform-node)

Please follow these steps to configure and run the sample code:

1. [Clone the repository](https://github.com/Jumio/perform-node) to a local directory
2. Run <code>npm install</code>
3. Take a look at the sample integration code in <code>./example/index.ts</code>
4. Copy <code>./example/config.skel.ts</code> to <code>./example/config.ts</code> and populate with your own API credentials and user agent 
5. Execute <code>npm run example</code>
6. Once complete, the outcome of the verification will be logged to the console
npm package: @jprox/mcp
Description: MCP Server for JProx - Japan Proxy Service for AI assistants
Author: JProx
Latest version: 0.1.4

# JProx MCP Server

MCP (Model Context Protocol) server for [JProx](https://jprox.dev) - enabling AI assistants to fetch content from Japanese geo-restricted websites.

## Installation

### Claude Desktop

Add to your Claude Desktop configuration (`~/.config/claude/claude_desktop_config.json` on Mac/Linux or `%APPDATA%\Claude\claude_desktop_config.json` on Windows):

```json
{
  "mcpServers": {
    "jprox": {
      "command": "npx",
      "args": ["-y", "@jprox/mcp"],
      "env": {
        "JPROX_API_KEY": "pk_your_api_key_here"
      }
    }
  }
}
```

### Getting Your API Key

1. Sign up at [jprox.dev](https://jprox.dev)
2. Get your API key from the [dashboard](https://jprox.dev/dashboard)
3. Add the key to your Claude Desktop config

**Free tier: 1,000 requests/month** - No credit card required!

## Tools

### `fetch_japan_site`

Fetch content from Japanese geo-restricted websites through JProx proxy.

**When to use:**
- When you get 403/Access Denied from Japanese sites
- When a site says "This service is only available in Japan"
- When scraping Japanese EC, job, or real estate sites

**Parameters:**
- `url` (required): The URL to fetch
- `format` (optional): Output format - `html`, `text`, or `json` (default: `text`)

**Example usage in Claude:**
> "Fetch the search results from Mercari for iPhone"
> "Get the latest job listings from Indeed Japan for software engineers"
> "Scrape property listings from SUUMO in Tokyo"

### `check_usage`

Check your API usage statistics.

**Returns:**
- Current plan
- Requests used this month
- Monthly limit
- Remaining requests

## Supported Sites

- **Mercari (メルカリ)** - Japanese marketplace
- **SUUMO (スーモ)** - Real estate listings
- **Rakuten (楽天市場)** - E-commerce
- **Yahoo! Shopping Japan**
- **Indeed Japan** - Job listings
- **Mynavi (マイナビ)** - Recruitment
- **Rikunabi (リクナビ)** - Recruitment
- And many more Japanese websites...

## Pricing

| Plan | Requests/Month | Price |
|------|----------------|-------|
| Free | 1,000 | $0 |
| Hobby | 10,000 | $19/month |
| Starter | 100,000 | $49/month |
| Pro | 500,000 | $149/month |

Upgrade at [jprox.dev/pricing](https://jprox.dev/pricing)

## Environment Variables

- `JPROX_API_KEY` (required): Your JProx API key
- `JPROX_BASE_URL` (optional): Custom API base URL (default: `https://api.jprox.dev`)

## Links

- Website: https://jprox.dev
- Dashboard: https://jprox.dev/dashboard
- Pricing: https://jprox.dev/pricing