open-index/open-npm huggingface dataset:
npm package: @samyan/gas-tracker
Description: Library for get gas price from different sources
Author: samyan
Latest version: 1.0.10


# GasTracker ![Version](https://img.shields.io/npm/v/@samyan/gas-tracker) ![License](https://img.shields.io/npm/l/@samyan/gas-tracker)

### Library for get gas price from different sources. The currently supported blockchains:

- Bitcoin
- Ethereum (requires **API TOKEN** from [etherscan.io](https://etherscan.io))
- Polygon (requires **API TOKEN** from [polygonscan.com](https://polygonscan.com))
- BNB Chain / Binance Smart Chain (requires **API TOKEN** from [bscscan.com](https://bscscan.com))

---

## Install

```sh
npm i @samyan/gas-tracker
```

## Usage

### Example 1

````typescript
const gasTracker = new GasTracker();

gasTracker
    .getBlockchain(BlockchainType.BITCOIN)
    .getPrices()
    .then((result: BitcoinResult) => {
        console.log(result.getRegularPrice());
    })
    .catch((error: any) => {
        console.log(error.message);
    });
````

--------------

### Example 2
````typescript
try {
    const gasTracker = new GasTracker('YOUR_API_TOKEN');

    const result = (await gasTracker
        .getBlockchain(BlockchainType.ETHEREUM)
        .getPrices()
    ) as EthereumResult;

    console.log(result.getFastPrice());
} catch (error) {
    console.log(error.message);
}
````
npm package: @samyca/mailflow
Description: A comprehensive tool for handling email flows in Node.js applications.
Author: Samyca
Latest version: 1.0.4

# @samyca/mailflow

A comprehensive tool for handling email flows in Node.js applications, providing functionalities for sending, receiving, and parsing emails with ease.

## Features

- Send emails using SMTP protocol.
- Fetch and parse emails from IMAP servers.
- Extract data from emails using CSS queries.
- Easy integration with Node.js applications.

## Installation

Install using npm:

```bash
npm install @samyca/mailflow
```

Or using yarn:

```bash
yarn add @samyca/mailflow
```

## Usage

### Creating an Account

```js
import { createAccount, createRandomAccount } from '@samyca/mailflow';

async function setupOtherAccount() {
  const account = await createRandomAccount();

  console.log(account);
}

async function setupAccount() {
  const account = await createAccount({
    smtpHost: 'smtp.example.com',
    smtpPort: 587,
    smtpSecure: true,
    imapHost: 'imap.example.com',
    imapPort: 993,
    imapSecure: true,
    username: 'your_username',
    password: 'your_password',
  });

  console.log(account);
}

setupOtherAccount().then();
setupAccount().then();
```

### Fetching and Parsing Emails

```js
import { createAccount } from '@samyca/mailflow';

async function getDataByCssQuery() {
  const account = await createAccount({
    imapHost: 'imap.example.com',
    imapPort: 993,
    imapSecure: true,
    username: 'your_username',
    password: 'your_password',
  });

  const lastEmail = await account.getLastMail({});
  const data = lastEmail.getData('div.code');

  console.log(data);
}
getDataByCssQuery().then();
```
npm package: @samyca/stratum-client
Description: A NodeJS based stratum client for communication with stratum pool
Author: Arnab Karmakar
Latest version: 1.2.0

# stratum-client
A NodeJS based stratum client for communication with stratum-capable pool.

## Installation

    $ npm i stratum-client --save

    const client = require('stratum-client');
    const Client = client({
      server: "grlcgang.com",
      port: 3333,
      worker: "KorkyMonster.testing",
      password: "x",
      autoReconnectOnError: true,
      onConnect: () => console.log('Connected to server'),
      onClose: () => console.log('Connection closed'),
      onError: (error) => console.log('Error', error.message),
      onAuthorizeSuccess: () => console.log('Worker authorized'),
      onAuthorizeFail: () => console.log('WORKER FAILED TO AUTHORIZE OH NOOOOOO'),
      onNewDifficulty: (newDiff) => console.log('New difficulty', newDiff),
      onSubscribe: (subscribeData) => console.log('[Subscribe]', subscribeData),
      onNewMiningWork: (newWork) => console.log('[New Work]', newWork),
      onSubmitWorkSuccess: (error, result) => console.log("Yay! Our work was accepted!"),
      onSubmitWorkFail: (error, result) => console.log("Oh no! Our work was refused because: " + error),
    });

Mining work can then be submitted through `Client.submit(["<worker>","<job_id>","<extranonce2>","<ntime>","<nonce>"]);` Worker must have been authorized correctly for work to register with a pool.

`worker` is required in order for `onNewMiningWork()` to receive new work continuously.

If `password` if not specified, the client will attempt to authenticate with 'x', which is good enough in most cases.

DEPRECATED: `onAuthorize(error, result)`. If `onAuthorizeSuccess` or `onAuthorizeFail` is not provided, it will fall back to `onAuthorize`.

## Development

    $ git clone https://github.com/arnabk/stratum-client
    $ cd stratum-client
    $ npm i

  For running int tests. Make sure that you use a valid stratum server details

    $ npm test

## Other information
The project is open for suggestion or feedback. If you notice any issues while developing or using this library, feel free to report it [here](https://github.com/arnabk/stratum-client/issues)
npm package: @samyeak/nepali-date-picker-mantine
Description: Nepali Calendars, date and time pickers based on Mantine components
Author: Samyeak
Latest version: 1.0.2

# Nepali Date picker using Mantine

## Installation

```bash
# With yarn
yarn add @mantine/core @mantine/hooks @samyeak/nepali-date-picker-mantine dayjs

# With npm
npm install @mantine/core @mantine/hooks @samyeak/nepali-date-picker-mantine dayjs

# with pnpm
pnpm add @mantine/core @mantine/hooks @samyeak/nepali-date-picker-mantine dayjs
```

# Usage

Please use the documentations here https://mantine.dev/dates/getting-started/

# Reference

Forked from [@vurilo](https://github.com/vurilo/nepali-date-picker)
npm package: @samypr100/vite-plugin-vue2
Description: > [!CAUTION] > Vue 2 has reached EOL, and this project is no longer actively maintained.
Author: Evan You
Latest version: 2.3.4-dev.0

# @samypr100/vite-plugin-vue2 [![npm](https://img.shields.io/npm/v/@samypr100/vite-plugin-vue2.svg)](https://npmjs.com/package/@samypr100/vite-plugin-vue2)

> [!CAUTION]
> Vue 2 has reached EOL, and this project is no longer actively maintained.

---

> Note: this plugin only works with Vue@^2.7.0.

```js
// vite.config.js
import vue from '@samypr100/vite-plugin-vue2'

export default {
  plugins: [vue()]
}
```

## Options

```ts
export interface Options {
  include?: string | RegExp | (string | RegExp)[]
  exclude?: string | RegExp | (string | RegExp)[]

  isProduction?: boolean

  // options to pass on to vue/compiler-sfc
  script?: Partial<Pick<SFCScriptCompileOptions, 'babelParserPlugins'>>
  template?: Partial<
    Pick<
      SFCTemplateCompileOptions,
      | 'compiler'
      | 'compilerOptions'
      | 'preprocessOptions'
      | 'transpileOptions'
      | 'transformAssetUrls'
      | 'transformAssetUrlsOptions'
    >
  >
  style?: Partial<Pick<SFCStyleCompileOptions, 'trim'>>
}
```

## Asset URL handling

When `@samypr100/vite-plugin-vue2` compiles the `<template>` blocks in SFCs, it also converts any encountered asset URLs into ESM imports.

For example, the following template snippet:

```vue
<img src="../image.png" />
```

Is the same as:

```vue
<script setup>
import _imports_0 from '../image.png'
</script>
```

```vue
<img :src="_imports_0" />
```

By default the following tag/attribute combinations are transformed, and can be configured using the `template.transformAssetUrls` option.

```js
{
  video: ['src', 'poster'],
  source: ['src'],
  img: ['src'],
  image: ['xlink:href', 'href'],
  use: ['xlink:href', 'href']
}
```

Note that only attribute values that are static strings are transformed. Otherwise, you'd need to import the asset manually, e.g. `import imgUrl from '../image.png'`.

## Example for passing options to `vue/compiler-sfc`:

```ts
import vue from '@samypr100/vite-plugin-vue2'

export default {
  plugins: [
    vue({
      template: {
        compilerOptions: {
          // ...
        },
        transformAssetUrls: {
          // ...
        }
      }
    })
  ]
}
```

## Example for transforming custom blocks

```ts
import vue from '@samypr100/vite-plugin-vue2'

const vueI18nPlugin = {
  name: 'vue-i18n',
  transform(code, id) {
    if (!/vue&type=i18n/.test(id)) {
      return
    }
    if (/\.ya?ml$/.test(id)) {
      code = JSON.stringify(require('js-yaml').load(code.trim()))
    }
    return `export default Comp => {
      Comp.i18n = ${code}
    }`
  }
}

export default {
  plugins: [vue(), vueI18nPlugin]
}
```

## License

MIT
npm package: @samyrai/component-contracts-cli
Description: CLI toolkit for component contracts catalog generation, baseline analysis, and codemods.
Latest version: 2.1.0

# @samyrai/component-contracts-cli

CLI for component-contracts workflows: catalog generation, baseline reporting, and codemods.

## Install

```bash
yarn add -D @samyrai/component-contracts-cli
```

or

```bash
npm install -D @samyrai/component-contracts-cli
```

## Commands

```bash
component-contracts --help
component-contracts catalog --repo . --ui-roots src/components/ui --out component-catalog.json
component-contracts baseline --repo . --config component-contracts.config.json --catalog component-catalog.json --out component-contracts-baseline.json
component-contracts codemod --repo . --config component-contracts.config.json --catalog component-catalog.json --report contracts-codemod-report.json
```

## Notes

- `catalog` scans component roots and emits a schema-versioned component catalog.
- `baseline` runs core engine analysis and emits machine-readable violation/bucket reports.
- `codemod` can run dry-run (default) or write mode (`--write`) for high-confidence replacements.

## Docs

- CLI migration tutorial: [https://github.com/SamyRai/html-to-components/blob/main/docs/tutorials/migrate-to-cli-commands.md](https://github.com/SamyRai/html-to-components/blob/main/docs/tutorials/migrate-to-cli-commands.md)
- Release tutorial: [https://github.com/SamyRai/html-to-components/blob/main/docs/tutorials/release-with-changesets-oidc.md](https://github.com/SamyRai/html-to-components/blob/main/docs/tutorials/release-with-changesets-oidc.md)
npm package: @samyrai/component-contracts-core
Description: Core utilities for component contracts cataloging, mapping, config, and baseline analysis.
Latest version: 2.1.0

# @samyrai/component-contracts-core

Shared runtime and schema utilities for component-contracts tooling.

This package is consumed by:

- `@samyrai/eslint-plugin-component-contracts`
- `@samyrai/component-contracts-cli`

## Install

```bash
yarn add @samyrai/component-contracts-core
```

or

```bash
npm install @samyrai/component-contracts-core
```

## Export Surface

- `@samyrai/component-contracts-core`
- `@samyrai/component-contracts-core/jsx-utils`
- `@samyrai/component-contracts-core/constants`
- `@samyrai/component-contracts-core/config-loader`
- `@samyrai/component-contracts-core/catalog-loader`
- `@samyrai/component-contracts-core/mapping-loader`
- `@samyrai/component-contracts-core/path-utils`
- `@samyrai/component-contracts-core/lib/*`
- `@samyrai/component-contracts-core/shared/*`

## Schemas

- `@samyrai/component-contracts-core/schemas/component-contracts.config.schema.json`
- `@samyrai/component-contracts-core/schemas/component-catalog.schema.json`
- `@samyrai/component-contracts-core/schemas/mapping-overrides.schema.json`

## Docs

- Architecture: [https://github.com/SamyRai/html-to-components/blob/main/docs/architecture.md](https://github.com/SamyRai/html-to-components/blob/main/docs/architecture.md)
npm package: @samyrai/eslint-plugin-component-contracts
Description: ESLint plugin for enforcing component-first JSX authoring with v5 policy-driven component contracts.
Latest version: 2.1.0

# @samyrai/eslint-plugin-component-contracts

ESLint plugin for enforcing component-first JSX authoring with policy-driven component contracts.

## Install

```bash
yarn add -D @samyrai/eslint-plugin-component-contracts
```

or

```bash
npm install -D @samyrai/eslint-plugin-component-contracts
```

## Flat Config Usage

```js
import { createComponentContractsConfig } from '@samyrai/eslint-plugin-component-contracts/config';

export default [
  ...createComponentContractsConfig({
    files: ['src/**/*.{ts,tsx,js,jsx}'],
    configPath: 'component-contracts.config.json',
    catalogPath: 'component-catalog.json',
    policyProfile: 'migration-default',
    minSuggestionConfidence: 0.75,
  }),
];
```

### Preset Variants

```js
import { flat } from '@samyrai/eslint-plugin-component-contracts/config';

export default [
  ...flat['recommended-warn'],
  // ...flat['recommended-error'],
  // ...flat['no-new-violations'],
];
```

## Rules

- `contracts/no-raw-html-in-features`
- `contracts/no-primitives-imports`
- `contracts/prefer-component-mapping`
- `contracts/no-layout-classes-on-box`
- `contracts/no-raw-motion-div-in-components`
- `contracts/no-typography-classes-on-layout-primitives`
- `contracts/prefer-semantic-layout-primitives`
- `contracts/prefer-text-component`

## Config Notes

- Config schema is v5 (breaking). Canonical fields only; legacy aliases were removed.
- `zones.profiles[].priority` is supported. Higher priority wins; on ties, the later profile wins.
- Primitive matcher canonical fields:
  - `matchImportedNames`
  - `allowInZones`
- Optional safe autofix target for `no-primitives-imports`:
  - `primitiveImportRule.rewrite.barrelImportPath`
  - Fixes apply only when imported names are statically resolvable from the barrel exports.

## Schemas

- `@samyrai/eslint-plugin-component-contracts/schemas/component-contracts.config.schema.json`
- `@samyrai/eslint-plugin-component-contracts/schemas/component-catalog.schema.json`
- `@samyrai/eslint-plugin-component-contracts/schemas/mapping-overrides.schema.json`

## Docs

- Architecture: [https://github.com/SamyRai/html-to-components/blob/main/docs/architecture.md](https://github.com/SamyRai/html-to-components/blob/main/docs/architecture.md)
- Implementation: [https://github.com/SamyRai/html-to-components/blob/main/docs/component-contracts-implementation.md](https://github.com/SamyRai/html-to-components/blob/main/docs/component-contracts-implementation.md)

## ESLint 10 Stack Notes

- Verified maintained/supported pairings for ESLint 10:
  - `@eslint-react/eslint-plugin` (React + hooks + DOM/Web API strict presets)
  - `eslint-plugin-unicorn`
  - `eslint-plugin-tailwindcss` (`flat/recommended` runtime validated with ESLint 10)
- `eslint-plugin-jsx-a11y` does not currently declare ESLint 10 peer support, so strict a11y in this stack should come from `@eslint-react` DOM safety rules until official support lands.
npm package: @samyssmile/quill-table-better
Description: A module that enhances the table functionality of Quill
Author: samyssmile
Latest version: 1.2.5

# Fork of quill-table-better
This is a fork of A module that enhances the table functionality of [Quill](https://quilljs.com/).

This module was original written by "attoae"

## Original Repository
https://github.com/attoae/quill-table-better
npm package: @samzong/feishu
Description: Production-grade Feishu/Lark channel plugin for Clawdbot
Latest version: 0.0.8
Deprecated: This package has moved to moltbot-channel-feishu. Run: clawdbot plugins install moltbot-channel-feishu

# clawdbot-plugin-feishu

**Turn Feishu into your AI super-gateway.** A production-grade Feishu/Lark channel plugin for [Moltbot](https://molt.bot) — the brilliant AI agent framework.

## Install

```bash
# npm
moltbot plugin install @samzong/feishu

# GitHub (for testing)
moltbot plugin install github:samzong/clawdbot-plugin-feishu
```

## Configure

Edit `~/.clawdbot/clawdbot.json`:

```json
{
  "channels": {
    "feishu": {
      "enabled": true,
      "appId": "cli_xxx",
      "appSecret": "xxx",
      "domain": "feishu",
      "dmPolicy": "pairing",
      "groupPolicy": "open"
    }
  }
}
```

Or use environment variables (takes precedence if config values are empty):

```bash
export FEISHU_APP_ID="cli_xxx"
export FEISHU_APP_SECRET="xxx"
```

### Configuration Options

| Field | Type | Default | Description |
|-------|------|---------|-------------|
| `enabled` | boolean | `false` | Enable/disable the channel |
| `appId` | string | - | Feishu App ID |
| `appSecret` | string | - | Feishu App Secret |
| `domain` | `"feishu"` \| `"lark"` | `"feishu"` | API domain (China / International) |
| `dmPolicy` | `"open"` \| `"pairing"` \| `"allowlist"` | `"pairing"` | DM access policy |
| `allowFrom` | string[] | `[]` | User IDs allowed for DM (when `dmPolicy: "allowlist"`) |
| `groupPolicy` | `"open"` \| `"allowlist"` \| `"disabled"` | `"allowlist"` | Group chat access policy |
| `groupAllowFrom` | string[] | `[]` | Group IDs allowed (when `groupPolicy: "allowlist"`) |
| `requireMention` | boolean | `true` | Require @mention in groups |

## Feishu App Setup

1. Go to [Feishu Open Platform](https://open.feishu.cn)
2. Create a self-built app
3. Enable permissions: `im:message`, `im:chat`, `contact:user.base:readonly`
4. Events → Use **Long Connection** mode
5. Subscribe to event: `im.message.receive_v1`
6. Get App ID and App Secret from **Credentials** page
7. Publish the app

## License

[MIT](LICENSE)
npm package: @san-dev/access-contract-decoder
Description: Auto-generated TypeScript types and utilities for AccessContract smart contract
Author: Your Name
Latest version: 1.0.0

# Generate Types 
## A generic package to help you create usable typescript functions and types for your blockchain contract

### Future Enhancements
- Make access-contract-decoder more generic, allow users to pass in contract information that allows the scripts to generate the src for any contract
- Add `generate-factory.ts`
  - Creates helper functions to connect to deployed contracts
- Add `generate-react-hooks.ts`
  - For React applications - creates custom hooks
npm package: @san-francisco/sf-docs-embeddings
Description: San Francisco documentation embeddings - example RAG data package
Author: Dan Lynch
Latest version: 0.3.1

<p align="center" width="100%">
  <img height="250" src="https://github.com/city-of-san-francisco/.github/blob/main/assets/logo.svg" />
</p>

<p align="center" width="100%">
   <a href="https://github.com/city-of-san-francisco/license"><img height="20" src="https://img.shields.io/badge/license-SF-blue.svg"/></a>
   <a href="https://github.com/city-of-san-francisco/sf-rag-utils/actions/workflows/ci.yml"><img height="20" src="https://github.com/city-of-san-francisco/sf-rag-utils/actions/workflows/ci.yml/badge.svg" /></a>
   <a href="https://www.npmjs.com/package/@san-francisco/sf-docs-embeddings"><img height="20" src="https://img.shields.io/github/package-json/v/city-of-san-francisco/sf-rag-utils?filename=packages%2Fsf-docs-embeddings%2Fpackage.json"/></a>
</p>

<p align="center" width="100%">
  <a href="https://github.com/city-of-san-francisco/sf-rag-utils">A pgpm workspace for building agentic, database-driven AI applications for the City of San Francisco.</a>
</p>

# @san-francisco/sf-docs-embeddings

San Francisco documentation embeddings - example RAG data package.

## Overview

This package demonstrates how to ship pre-computed embeddings as PGPM migrations. It creates a sample collection with San Francisco city documentation and example embeddings.

## What This Package Does

1. Creates an embedding model configuration for `text-embedding-3-small`
2. Creates the `sf-docs` collection with semantic chunking config
3. Seeds example documents and chunks
4. (In production) Would include actual vector embeddings

## Usage

```bash
# Install the RAG schema first
pgpm deploy @sf-ai/rag-core

# Then install this data package
pgpm deploy @san-francisco/sf-docs-embeddings
```

## Data Structure

After installation, you'll have:

- **Collection**: `sf-docs` - San Francisco city documentation
- **Model**: `text-embedding-3-small` (OpenAI, 1536 dimensions)
- **Documents**: Example SF city services content
- **Chunks**: Semantically chunked document segments

## Creating Your Own Data Package

To create a similar data package for your own embeddings:

1. Generate embeddings using your preferred model
2. Export using `rag.export_collection_json()`
3. Convert the JSON to SQL INSERT statements
4. Package as a PGPM module

Example workflow:
```sql
-- Export your collection
SELECT rag.export_collection_json('your-collection-id');

-- Or export as CSV for processing
SELECT * FROM rag.export_embeddings_csv('your-collection-id');
```

## Dependencies

- `@sf-ai/rag-core`

## License

[SF License](https://github.com/city-of-san-francisco/license)
npm package: @san-siva/blogkit-md-cli
Description: CLI tool to preview markdown files as blogkit-md blog posts
Latest version: 0.1.14

---
title: blogkit-md-cli
description: A CLI tool to preview markdown files as blogkit-md blog posts in your browser with live reload.
---

# blogkit-md-cli

A CLI tool to preview markdown files as [blogkit-md](https://www.npmjs.com/package/@san-siva/blogkit-md) blog posts in your browser with live reload.

## Installation

```bash
npm install -g @san-siva/blogkit-md-cli
```

## Usage

```bash
blogkit-md <path-to-markdown-file> [--port=<port>]
```

### Arguments

| Argument                  | Description                                                   |
| ------------------------- | ------------------------------------------------------------- |
| `<path-to-markdown-file>` | Path to the markdown file to preview                          |
| `--port=<port>`           | Port to run the preview server on (default: random free port) |

### Examples

```bash
# Preview a markdown file
blogkit-md ./posts/my-post.md

# Preview on a specific port
blogkit-md ./posts/my-post.md --port=3001
```

The browser will open automatically once the server is ready. The preview reloads whenever you save changes to the markdown file.

## Requirements

- Node.js >= 18.0.0

## License

[MIT](./LICENSE)
npm package: @san0072/sketch-canvas
Description: sync sketch react-native canvas
Author: SAN
Latest version: 0.0.1

# sketch-sync-canvas

#### Description
sync sketch react native canvas

#### Software Architecture
Software architecture description

#### Installation

1.  xxxx
2.  xxxx
3.  xxxx

#### Instructions

1.  xxxx
2.  xxxx
3.  xxxx

#### Contribution

1.  Fork the repository
2.  Create Feat_xxx branch
3.  Commit your code
4.  Create Pull Request


#### Gitee Feature

1.  You can use Readme\_XXX.md to support different languages, such as Readme\_en.md, Readme\_zh.md
2.  Gitee blog [blog.gitee.com](https://blog.gitee.com)
3.  Explore open source project [https://gitee.com/explore](https://gitee.com/explore)
4.  The most valuable open source project [GVP](https://gitee.com/gvp)
5.  The manual of Gitee [https://gitee.com/help](https://gitee.com/help)
6.  The most popular members  [https://gitee.com/gitee-stars/](https://gitee.com/gitee-stars/)