open-index/open-npm huggingface dataset:
npm package: @pettarn/f-router
Description: [![npm version](https://badge.fury.io/js/%40pettarn%2Ff-router.svg)](https://badge.fury.io/js/%40pettarn%2Ff-router)
Latest version: 1.3.3

##    __f-router__

[![npm version](https://badge.fury.io/js/%40pettarn%2Ff-router.svg)](https://badge.fury.io/js/%40pettarn%2Ff-router)


***

> `f-router` is a router for Vue.js

##  Feature

-   support router children
-   router redirect
-   router-link tag
-   router-view tag
  

##  Install

    npm install @pettarn/f-router

##  Quick Start


    import Vue from 'vue'
    import FRouter from '@pettarn/f-router'

    import indexPage from '../components/indexPage.vue'
    import male from '../components/male.vue'
    import female from '../components/female.vue'

    Vue.use(FRouter)

    let routes = [
        {
            path: '',
            redirect: '/sex/'
        },
        {
            path: '/sex/',
            component: indexPage,
            children: [
                {
                    path: 'a',
                    component: male
                },
                {
                    path: 'b',
                    component: female
                }
            ]
        },
    ]

    let router = new FRouter({
        routes
    })

    export default router

##   App.vue

    <template>
    <div id="app">
        <h3>Following is router render component.</h3>
        <router-view></router-view>
    </div>
    </template>

## router-link tag


    <router-link to="/sex/a" tag="span">男</router-link>
    or
    <router-link to="/sex/b" tag="span">女</router-link>

## Standard

### MIT
npm package: @pettarn/vue-router-slider
Description: A Vue.js project
Author: Pettarn
Latest version: 1.0.2

# vue-router-slider

> A Vue.js project

## Build Setup

``` bash
# install dependencies
npm install

# serve with hot reload at localhost:8080
npm run dev

# build for production with minification
npm run build
```

For detailed explanation on how things work, consult the [docs for vue-loader](http://vuejs.github.io/vue-loader).
npm package: @pettry-solutions/scripts
Description: Modular CLI tools for various utilities
Author: Dakotah Pettry
Latest version: 1.0.2

# @pettry-solutions/scripts

A modular CLI toolkit for analyzing and understanding JavaScript/TypeScript codebases.

## Installation

```bash
npm install -g @pettry-solutions/scripts
```

Or use directly with npx:

```bash
npx @pettry-solutions/scripts <command>
```

## Available Tools

### Import Mapping

Analyze import patterns across your JavaScript/TypeScript repositories to understand which exports from your packages are actually being used.

**Use cases:**
- Identify which exports from your packages are being consumed
- Discover unused exports that can be safely removed
- Understand import patterns across multiple repositories
- Audit package usage in a monorepo

#### Usage

```bash
ztc import-mapping <configPath>
```

#### Configuration

Create a JSON configuration file:

```json
{
  "repositories": [
    "path/to/repo-1",
    "path/to/repo-2"
  ],
  "packages": [
    "path/to/package-1"
  ],
  "packageNames": [
    "@yourorg/ui",
    "@yourorg/utils"
  ],
  "ignorePatterns": [
    "node_modules",
    "dist",
    "build"
  ],
  "outputDir": "./output"
}
```

| Option | Required | Description |
|--------|----------|-------------|
| `repositories` | Yes | Array of repository paths to analyze |
| `packages` | Yes | Array of standalone package paths to analyze |
| `packageNames` | Yes | Package names to track imports for |
| `ignorePatterns` | No | Directories to skip (defaults: `node_modules`, `dist`, `build`, `.next`, `coverage`) |
| `outputDir` | Yes | Directory for output JSON files |

#### Output

The tool generates JSON output files containing:
- All imported values organized by repository and file
- Export usage statistics
- Summary of package utilization

#### Supported Import Syntaxes

- Named imports: `import { Button, Input } from '@pkg/ui'`
- Namespace imports: `import * as utils from '@pkg/utils'`
- Default imports: `import React from 'react'`
- Type imports: `import type { User } from '@pkg/core'`
- Subpath imports: `import { validate } from '@pkg/utils/validators'`
- Multi-line imports
- Mixed imports: `import React, { useState } from 'react'`

## License

MIT
npm package: @peulda/channel-io-sdk
Description: Unofficial channel.io SDK
Author: peulda
Latest version: 1.0.5

# `@peulda/channel-io-sdk`
> Unofficial [channel.io](https://channel.io) SDK for npm

# Usage
### loadChannel (Recommended)
```ts
import { loadChannel } from '@peulda/channel-io-sdk'

// with async-await
async function main() {
  const channel = loadChannel()

  await channel.boot({
    pluginKey: 'YOUR_PLUGIN_KEY',
  })

  await channel.updateUser(userInfo)
}

// with Promise
const channel = loadChannel()
channel
  .boot({
    pluginKey: 'YOUR_PLUGIN_KEY',
  })
  .then(() => {
    // ...
  })
```

### loadSDK
```ts
import { loadSDK } from '@peulda/channel-io-sdk'

loadSDK()

window.ChannelIO('boot', {
  pluginKey: 'YOUR_PLUGIN_KEY',
})
```

# LICENSE
[MIT](LICENSE)

Disclaimer: _This is not an officially supported Channel.io product._
npm package: @peulda/channel-io-types
Description: Unofficial channel.io SDK types
Author: peulda
Latest version: 1.0.1

# `@peulda/channel-io-types`

> Unofficial [channel.io](https://channel.io) type definition

## Usage
```ts
import '@peulda/channel-io-types'

// Now you can use window.ChannelIO with typescript
```
npm package: @pevil/media-query
Description: Conditionally render dom elements based on media queries in Angular2+
Author: Peter Laraia
Latest version: 1.0.0

# Angular Media Queries

Similar to the *ngIf structural directive, only render dom elements if they match a media query using the *ifMediaQuery directive

## Install

`$ npm install @pevil/media-query`

## Usage

First import the MediaQueryModule,

```
import { MediaQueryModule } from '@pevil/media-query';

@NgModule({
    imports: [MediaQueryModule],
    exports: [MediaQueryModule] //if added to a SharedModule
})
export class SharedModule {}
```

then use it in your html template:

```
<img *ifMediaQuery="'(min-width: 470px)'" [src]="item?.imageUrl"
```

## Example

https://embed.plnkr.co/Cn2BvZlcCSXehPrSDZcO/
npm package: @pevil/ng-tabs
Description: Angular2+ UI directives for constructing tab interfaces
Author: Peter Laraia
Latest version: 1.0.0

# Angular UI Tabs

## Install

`$ npm install @pevil/ng-tabs`

## Usage

### Import

First, import the provided module:

```
import { NgTabModule } from '@pevil/ng-tabs';

@NgModule({
    imports: [NgTabModule]
})
export class Module {}
```

### Building a set of tabs

3 directives are provided:
* pvlTabGroup
* pvlTab
* pvlTabPanel

First, an example of how to use them together, with more detail below

```
<ul pvlTabGroup [tabPanel]="characterPanel">
    <li pvlTab [tabId]="'a'">
        View A
        <ng-template><a-component></a-component></ng-template>
    </li>
    <li pvlTab [tabId]="'b'">
        View B
        <ng-template><b-component></b-component></ng-template>
    </li>
    <li pvlTab [tabId]="'c'">
        View C
        <ng-template><img [src]="c" /></ng-template>
    </li>
</ul>

<div>some other optional content that maybe you want to place before the tab panel</div>

<ng-template pvlTabPanel #putContentHere="pvlTabPanel"></ng-template>
```

For a more concrete example, see [here](https://github.com/Pevil/ng-tabs/blob/master/demo/src/demo.component.ts) or [here](https://embed.plnkr.co/1uobXAT1HiGv8YTpz8KS)

*pvlTabGroup*
Use this to define a group of tabs that belong together. Here, we're defining an <ul> element as the group, where each
child with the pvlTab directive (in this case each <li> element), is a part of this tabGroup.

The [tabPanel] input expects a reference to the panel where we want to render these tabs.
The optional [initialTab] input expects a string matching the tabId of whichever tab should be displayed first. If none is provided, the first tab's contents will be the default.

*pvlTab*
As described above, we want to apply the pvlTab directive to each element that describes a tab. In this case we have 3 <li> elements, where the tabs themselves will display [View A, View B, View C]. Each element with a pvlTab directive also uses an <ng-template> to define the data that should be rendered in the panel when the tab is selected.

The [tabId] input expects a string id, unique to the other tabs in this tab group.

Whichever tab is active will have the css class `.pvl-active-tab` applied to it

*pvlTabPanel*
Apply this to an <ng-template> element, wherever you want the content defined by each tab to render. Also remember to grab a reference to the directive, in order to pass that as an input to the tabGroup directive (in our example, we did that with #putContentHere="pvlTabPanel")

## Demo
Run local demo by:
1. Cloning the repo
2. Run `$ npm run build.all`
3. `cd demo`
4. `python3 -m http.server 4300`
5. open localhost:4300 in a browser

OR
visit this [plunkr](https://embed.plnkr.co/1uobXAT1HiGv8YTpz8KS)
npm package: @pewterzz/karp
Description: Local-first LLM CLI for instant command recall
Author: pewterzz
Latest version: 1.0.4

# karp

A local-first CLI that recalls shell commands using a local LLM. Ask in plain English, get back the exact command — nothing else.

```
karp "how do I check disk usage"
# df -h
```

No cloud. No subscriptions. Runs against any llama.cpp or Ollama server.

---

## Requirements

- Node.js 18+
- A running llama.cpp or Ollama instance (local or on your network)

---

## Install

```bash
npm install -g @pewterzz/karp
```

---

## Setup

Point karp at your LLM server:

```bash
karp config url http://localhost:8080/v1/chat/completions
karp config model your-model-name.gguf
```

For Ollama, the URL is typically `http://localhost:11434/v1/chat/completions`.

Config is stored at `~/.karp/config.json`.

---

## Usage

### Ask a question

```bash
karp "how do I recursively copy a folder"
# cp -r src/ dest/
```

The model returns only the command. If you include words like "explain" or "what does", it gives a one-sentence description instead.

### Store a command

```bash
karp store "docker run -d -p 3000:8080 ghcr.io/open-webui/open-webui:main"
```

Stored commands are used as context when you ask questions. The more you store, the better karp gets at recalling your specific setup.

### List stored commands

```bash
karp list
# 1. docker run -d -p 3000:8080 ghcr.io/open-webui/open-webui:main
# 2. df -h
# ...
```

### Remove a stored command

```bash
karp remove 2
```

### Repeat the last answer

```bash
karp last
```

Prints the previous response instantly — no LLM call.

### View or change config

```bash
karp config                        # show all config
karp config url <url>              # set server URL
karp config model <model>          # set model name
karp config top_k <n>              # results sent to LLM (default: 10)
karp config threshold <n>          # store size before BM25 kicks in (default: 15)
```

---

## How it works

Queries go to your local LLM with a strict system prompt that enforces command-only output. When your store grows past `threshold` entries, karp runs **BM25** over your saved commands to find the most relevant ones before sending them as context — keeping prompts short and responses accurate.

All data lives in `~/.karp/`:

| File | Purpose |
|---|---|
| `config.json` | Server URL, model, and tuning options |
| `commands.md` | Your stored commands |
| `.last` | Cache of the last response |

---

## License

MIT
npm package: @pexcode/qds-print-sdk
Description: SDK for printing shipping labels with QR codes , This is a TypeScript library published under an pexcode to help users and developers to use quickdeliverysystem print.
Author: Mussab Muhaimeed
Latest version: 3.5.3

# QDS Print SDK

**pexcode.com** · **quickdeliverysystem.com**

TypeScript SDK for printing Quick Delivery System shipping labels to thermal printers using **QZ Tray** and **ESC/POS** commands. Labels include recipient/sender/shipping details, a scannable QR code, and formatted date.

---

## Install

```bash
npm i @pexcode/qds-print-sdk
```

or

```bash
npm i --save @pexcode/qds-print-sdk
```

---

## Requirements

- **QZ Tray** must be installed and running on the machine (download from [qz.io](https://qz.io)).
- A thermal printer (58mm or 80mm) configured and available to QZ Tray.

---

## Usage

### Basic

```ts
import QDSPrint, { type PrintData } from "@pexcode/qds-print-sdk";

// printerName: exact or partial name as shown in QZ Tray
// printerSize: "58mm" or "80mm" (default: "80mm")
const printer = new QDSPrint("My Thermal Printer", "80mm");

const data: PrintData = {
  id: "123456",
  uuid: "abcd-efgh-ijkl",
  dest_name: "John Doe",
  dest_address: "123 Main St, Paris",
  sender_name: "Jane Smith",
  sender_address: "45 Rue de Lyon, Paris",
  created_at: new Date().toISOString(),
  shipping: {
    name: "QDS Warehouse",
    address: "456 Route de Lille, France",
    id: "WH-001",
  },
};

// Single label
await printer.print(data);

// Multiple labels (printed in sequence)
await printer.printBulk([data, data2, data3]);
```

### Printer size

- **`"80mm"`** (default): wider line, larger QR code.
- **`"58mm"`**: narrower line, smaller QR for narrow rolls.

```ts
const printer58 = new QDSPrint("My 58mm Printer", "58mm");
const printer80 = new QDSPrint("My 80mm Printer"); // 80mm by default
```

### Error handling (QZ Tray not running)

```ts
import QDSPrint, { QZTrayNotRunningError } from "@pexcode/qds-print-sdk";

const printer = new QDSPrint("My Printer", "80mm");

try {
  await printer.print(data);
} catch (err) {
  if (err instanceof QZTrayNotRunningError) {
    console.error("Start QZ Tray and try again.");
  } else {
    throw err;
  }
}
```

## Types

| Type | Description |
|------|-------------|
| `PrintData` | Full label payload: id, uuid, dest_*, sender_*, created_at, shipping |
| `ShippingInfo` | shipping.name, shipping.address, shipping.id |
| `PrinterSize` | `"58mm" \| "80mm"` |

---

## Note

This package provides the **Quick Delivery System** label format and is not intended to be customized. If you need the same layout for your own system, you can still use the SDK as-is.