open-index/open-npm huggingface dataset:
npm package: @jccdex/triangular-arbitrage
Description: triangular arbitrage
Author: JCCDex
Latest version: 1.0.8

<!-- markdownlint-disable MD033 -->

# triangular-arbitrage

![npm](https://img.shields.io/npm/v/@jccdex/triangular-arbitrage.svg)
[![Build Status](https://travis-ci.com/JCCDex/jcc-triangular-arbitrage.svg?branch=master)](https://travis-ci.com/JCCDex/jcc-triangular-arbitrage)
[![Coverage Status](https://coveralls.io/repos/github/JCCDex/jcc-triangular-arbitrage/badge.svg?branch=master)](https://coveralls.io/github/JCCDex/jcc-triangular-arbitrage?branch=master)

## Arbitrage Process

`BTC-ETH-USDT` as an example.

<img src="images/arbitrage-process.png" alt="Arbitrage Process" width="600">

## Installtion

```shell
npm install @jccdex/triangular-arbitrage
```
npm package: @jccdn/tokenflow
Description: Zero-config CLI to pull all Figma variables and generate CSS, TypeScript, Tailwind and JSON token artifacts.
Latest version: 0.1.0

# tokenflow

Zero-config CLI to pull all variables from a Figma file and generate CSS custom properties, TypeScript exports, Tailwind config, and JSON artifacts.

No manual mapping needed — variable names are normalized automatically from your Figma structure.

## Install

```bash
npm install -g tokenflow
```

## Usage

```bash
tokenflow pull     # fetch all variables from Figma → tokens.snapshot.json
tokenflow build    # generate output files from snapshot
tokenflow sync     # pull + build in one step
```

## Setup

**1. Get a Figma personal access token**
Figma → Settings → Security → Personal access tokens

**2. Get your Figma file key**
From the URL: `figma.com/design/`**`FILE_KEY`**`/filename`

**3. Create `tokens.config.json`**

```json
{
  "figmaFileKey": "your-file-key",
  "output": [
    { "format": "css",      "file": "src/tokens/variables.css" },
    { "format": "ts",       "file": "src/tokens/index.ts" },
    { "format": "tailwind", "file": "src/tokens/tailwind.ts" },
    { "format": "json",     "file": "src/tokens/tokens.json" }
  ]
}
```

**4. Pull and build**

```bash
FIGMA_TOKEN=your_token tokenflow sync
```

## Variable name normalization

Figma variable paths are normalized automatically:

| Figma collection | Figma variable | CSS variable | TS path |
|-----------------|----------------|--------------|---------|
| `Colors` | `Brand/Primary` | `--colors-brand-primary` | `tokens.colors.brand.primary` |
| `Spacing` | `4` | `--spacing-4` | `tokens.spacing["4"]` |
| `Radius` | `Md` | `--radius-md` | `tokens.radius.md` |

## Multi-mode / Theming

If your Figma collection has multiple modes (e.g. `Light` / `Dark`), the CSS output handles it automatically:

```css
:root {
  --colors-brand-primary: #1a73e8;
}

[data-theme="dark"] {
  --colors-brand-primary: #8ab4f8;
}
```

Switch themes at runtime:
```js
document.documentElement.dataset.theme = "dark";
```

## Output formats

| Format | Output |
|--------|--------|
| `css` | CSS custom properties with multi-mode support |
| `ts` | TypeScript `tokens` (raw values) + `cssVars` (var references) |
| `json` | Raw token values with all modes |
| `tailwind` | Tailwind `theme.extend` config with CSS var references |

## Config reference

| Field | Required | Default | Description |
|-------|----------|---------|-------------|
| `figmaFileKey` | yes | — | Figma file key from URL |
| `output` | yes | — | Array of `{ format, file }` |
| `snapshot` | no | `tokens.snapshot.json` | Snapshot file path |
| `cssPrefix` | no | `""` | Prefix for CSS variable names (e.g. `"app"` → `--app-colors-brand-primary`) |

## Add to package.json

```json
{
  "scripts": {
    "tokens:pull": "tokenflow pull",
    "tokens:build": "tokenflow build",
    "tokens:sync": "tokenflow sync"
  }
}
```

## Environment

```bash
FIGMA_TOKEN=your_token   # required for pull and sync
```
npm package: @jccham/capacitor-pdf-viewer
Description: Native PDF viewer
Author: jesus-chacon
Latest version: 0.0.9

# @jccham/capacitor-pdf-viewer

Native PDF viewer

## Install

```bash
yarn add @jccham/capacitor-pdf-viewer
npx cap sync
```

## API

<docgen-index>

* [`open(...)`](#open)
* [`close()`](#close)

</docgen-index>

<docgen-api>
<!--Update the source file JSDoc comments and rerun docgen to update the docs below-->

### open(...)

```typescript
open(params: { url: string; title?: string; top?: number; }) => Promise<void>
```

| Param        | Type                                                        |
| ------------ | ----------------------------------------------------------- |
| **`params`** | <code>{ url: string; title?: string; top?: number; }</code> |

--------------------


### close()

```typescript
close() => Promise<void>
```

--------------------

</docgen-api>
npm package: @jcdomber/grte-cat-menu
Description: Webcomponent grte-cat-menu following open-wc recommendations
Author: grte-cat-menu
Latest version: 0.1.4

# \<grte-cat-menu>

This webcomponent follows the [open-wc](https://github.com/open-wc/open-wc) recommendation.

Row in a table containing the information of a menu category:
- Category
- Order number shown on the printout
- Total elements that make up the category

e.g : Desserts - 12 - 22

## Installation
```bash
npm i @jcdomber/grte-cat-menu
```

## Usage
```html
<script type="module">
  import 'grte-cat-menu/grte-cat-menu.js';
</script>

<grte-cat-menu
        category="Pescados"
        order=11
        totProds=10
        @get-category-delete=${getEventDelete}
        @get-category-edit=${getEventEdit}>
      </grte-cat-menu>
      
```
## Properties

      category: String
      order:    Number
      totProds: Number

## Events

@click on the edit button. Expose the event: `get-category-edit`

detail: 
- selected category
- selected order

@click on the cancel button. Expose the event: `get-category-delete`

detail: 
- selected category
- selected order


## Tooling configs

For most of the tools, the configuration is in the `package.json` to reduce the amount of files in your project.

If you customize the configuration a lot, you can consider moving them to individual files.

## Local Demo with `es-dev-server`
```bash
npm run start
```
To run a local development server that serves the basic demo located in `demo/index.html`
npm package: @jcdomber/grte-man-cat-menu
Description: Webcomponent grte-man-cat-menu following open-wc recommendations
Author: grte-man-cat-menu
Latest version: 0.1.1

# \<grte-man-cat-menu>

This webcomponent follows the [open-wc](https://github.com/open-wc/open-wc) recommendation.

This component can change an existing category and can also add a new menu category.
- Category
- Order number shown on the printout

## Installation
```bash
npm i @jcdomber/grte-man-cat-menu
```

## Usage
```html
<script type="module">
  import 'grte-man-cat-menu/grte-man-cat-menu.js';
</script>

<grte-man-cat-menu
    category="Ensaladas"
    order=2
    @get-category=${getEventDetail}>
</grte-man-cat-menu>
```
## Properties

      category: String
      order:    Number

## Events

@click on the SAVE button. Expose the event: `get-category`

detail: 
- edited category
- edited order


## Tooling configs

For most of the tools, the configuration is in the `package.json` to reduce the amount of files in your project.

If you customize the configuration a lot, you can consider moving them to individual files.

## Local Demo with `es-dev-server`
```bash
npm run start
```
To run a local development server that serves the basic demo located in `demo/index.html`
npm package: @jcdomber/grte-tab-cat-menu
Description: Webcomponent grte-tab-cat-menu following open-wc recommendations
Author: grte-tab-cat-menu
Latest version: 0.1.2

# \<grte-tab-cat-menu>

This webcomponent follows the [open-wc](https://github.com/open-wc/open-wc) recommendation.

This component, as a table, contains n-rows, each row:
```html
 <grte-cat-menu>
```
You receive as an entry a table of objects, where each object is a category.

e.g.:

```html
const stringArrayCategorias = '[ {"category": "Postres", "order": 20, "totProds": 10} , {"category": "Bebidas",  "order": 15, "totProds": 25}, {"category": "Primeros", "order": 10, "totProds": 12}, {"category": "Entrates", "order": 1, "totProds": 5}]';
```

## Installation
```bash
npm i @jcdomber/grte-tab-cat-menu
```

## Usage
```html
<script type="module">
  import 'grte-tab-cat-menu/grte-tab-cat-menu.js';
</script>

<grte-tab-cat-menu
  .relCategories=${JSON.parse(stringArrayCategorias)}
  @get-category-delete=${getEventDelete}
  @get-category-edit=${getEventEdit}>
</grte-tab-cat-menu>
```


## Properties

  relCategories: Array

## Events

@click on the edit button. Expose the event: `get-category-edit`

detail: 
- selected category
- selected order

@click on the cancel button. Expose the event: `get-category-delete`

detail: 
- selected category
- selected order


## Tooling configs

For most of the tools, the configuration is in the `package.json` to reduce the amount of files in your project.

If you customize the configuration a lot, you can consider moving them to individual files.

## Local Demo with `es-dev-server`
```bash
npm run start
```
To run a local development server that serves the basic demo located in `demo/index.html`
npm package: @jcedb07/ced-cli
Description: Personal CLI for Frontend boilerplates
Author: Ced
Latest version: 1.2.0

# ced-cli

My personal frontend template boilerplate CLI

## Installation

Use npm to install ced-cli.

```
npm install @jcedb07/ced-cli -g
```

## Usage

```cli
% ced

    ____         _      _      _                ____                           _
  / ___|___  __| |_ __(_) ___| | __           / ___|_      ____ _ _ __   ___ | |
 | |   / _ \/ _` | '__| |/ __| |/ /____ _____| |  _\ \ /\ / / _` | '_ \ / _ \| |
 | |__|  __/ (_| | |  | | (__|   <_____|_____| |_| |\ V  V / (_| | |_) | (_) |_|
  \____\___|\__,_|_|  |_|\___|_|\_\           \____| \_/\_/ \__,_| .__/ \___/(_)
                                                                 |_|

? Pili ug framework nimo bossing: (Use arrow keys)
❯ react
  react-native
```