open-index/open-npm huggingface dataset:
npm package: @presentdata/cli
Description: Currently (in order to keep the build setup minimal) this CLI package only contains the CLI source but cannot be run directly. Instead it needs to be built & run via `packages/presentdata`.
Latest version: 0.1.0

# @presentdata/cli

Currently (in order to keep the build setup minimal) this CLI package only contains the CLI source but cannot be run directly. Instead it needs to be built & run via `packages/presentdata`.
npm package: @presetai/search
Description: A React component for intergrating [PresetAI](https://thepresetai.com/) Search into your React application.
Author: ZanyuanYang
Latest version: 1.0.10

# PresetAI Search

A React component for intergrating [PresetAI](https://thepresetai.com/) Search into your React application.


## Installation

```bash
npm install @presetai/search
```

## Documentation

> upcoming...

## Usage

```jsx
import { PresetAISearchBar } from '@presetai/search';

<PresetAISearchBar user_api_key="YOUR_USER_API_KEY" project_api_key="YOUR_PROJECT_API_KEY" />
```
npm package: @preskok-org/ui
Description: Add components to your apps.
Latest version: 0.1.3

# preskok

A CLI for adding components to your project.

## Usage

Use the `init` command to initialize dependencies for a new project.

The `init` command installs dependencies, adds the `cn` util, configures `tailwind.config.js`, and CSS variables for the project.

```bash
npx preskok init
```

## add

Use the `add` command to add components to your project.

The `add` command adds a component to your project and installs all required dependencies.

```bash
npx preskok add [component]
```

### Example

```bash
npx preskok add alert-dialog
```

You can also run the command without any arguments to view a list of all available components:

```bash
npx preskok add
```

## Documentation

Visit https://ui-three-mu.vercel.app/docs/cli to view the documentation.

## License

Licensed under the [MIT license](https://github.com/shadcn/ui/blob/main/LICENSE.md).
npm package: @press2ai/theme-specialist-glossy
Description: Classless, AI-first glossy theme. Framework-agnostic templates (Hono, Astro, raw HTML). Semantic HTML, Schema.org microdata, JSON-LD — built for LLM crawlers.
Latest version: 0.11.9

# @press2ai/theme-specialist-glossy

Classless, AI-first theme. Semantic HTML + Schema.org + JSON-LD. Works with **Hono**, **Astro**, or any framework that outputs HTML.

## Install

```bash
npm install @press2ai/theme-specialist-glossy
```

## Usage — Hono / Cloudflare Workers

```ts
import { layout, profileCard, profileArticle } from '@press2ai/theme-specialist-glossy/templates';

app.get('/', (c) => c.html(layout({ title: 'Katalog' }, cards)));
app.get('/:slug', (c) => c.html(layout({ title: name }, profileArticle(profile))));
```

## Usage — Astro

```astro
---
import Layout from '@press2ai/theme-specialist-glossy/Layout.astro';
import ProfileArticle from '@press2ai/theme-specialist-glossy/ProfileArticle.astro';
import '@press2ai/theme-specialist-glossy/styles/glossy.css';
---
<Layout title={name}>
  <ProfileArticle profile={profile} />
</Layout>
```

## Exports

| Path | What |
|---|---|
| `@press2ai/theme-specialist-glossy` | `profileSchema`, `Profile` type, `getJsonLd`, `getAiManifest` |
| `@press2ai/theme-specialist-glossy/templates` | `layout`, `hero`, `profileCard`, `profileArticle` |
| `@press2ai/theme-specialist-glossy/styles/glossy.css` | Classless CSS (~12 KB, no JS) |
| `@press2ai/theme-specialist-glossy/*.astro` | Astro wrappers (thin, call templates internally) |

## Architecture

```
CSS (glossy.css) ← classless, styles by semantic tags
        ↑
  templates/*.ts  ← pure functions → HTML strings (single source of truth)
        ↑
  components/*.astro ← thin wrappers for Astro DX
```

One set of templates, zero divergence between frameworks.

## Hosting compatibility

| Platform | Runtime | What you get |
|---|---|---|
| **GitHub Pages** (Astro) | Static / SSG | Pre-built HTML + CSS. Zero cost, zero backend. Profile pages generated at build time from `profile.json`. |
| **Cloudflare Workers** (Hono) | Edge SSR | Dynamic HTML from D1/KV. Database queries, opt-out forms, API endpoints (`catalog.json`, `llms.txt`). Free tier: 100k req/day. |
| **Cloudflare Pages** (Astro SSR) | Edge SSR | Astro with `@astrojs/cloudflare` adapter. D1/KV bindings via `Astro.locals`. Middle ground — Astro DX + edge database. |

**GitHub Pages** = static profiles, no server needed. Good for claimed/verified personal pages.

**Cloudflare Workers** = full SSR, database, forms, API. Good for catalogs, directories, dynamic listings. Templates work directly — `c.html(layout(...))`.

**Cloudflare Pages** = if you want Astro's routing/islands AND server-side data. Same templates under the hood, Astro components on top.

## License

MIT
npm package: @pressa/cli
Description: CLI for Pressa — Compile-as-a-Service. LaTeX in, PDF out.
Author: Pressa
Latest version: 0.1.1

# Pressa CLI

Command-line interface for [Pressa](https://pressa.dev) - Compile-as-a-Service. LaTeX in, PDF out.

## Installation

```bash
npm install -g @pressa/cli
```

## Quick Start

```bash
# Set your API key
pressa auth

# Compile a LaTeX file
pressa compile report.tex

# Compile with a specific engine
pressa compile report.tex --compiler xelatex

# Read from stdin
cat report.tex | pressa compile -

# JSON output (for AI agents)
pressa compile report.tex --json
```

## Commands

### `pressa auth`

Configure your API key.

```bash
# Interactive
pressa auth

# Non-interactive
pressa auth --key pressa_xxxx
```

### `pressa compile <file>`

Compile a LaTeX file to PDF.

| Option | Description |
|--------|-------------|
| `-c, --compiler` | LaTeX compiler: `pdflatex` (default), `xelatex`, `lualatex` |
| `-o, --output` | Output PDF filename |
| `--json` | Machine-readable JSON output |
| `--no-download` | Don't download PDF, just return URL |
| `-u, --url` | API base URL override |

Use `-` as filename to read from stdin.

### `pressa usage`

Show your API usage statistics.

```
Plan:    free
Used:    3/100 this month
Resets:  April 30, 2026
API Key: pressa_c... (Test Key)
```

## Configuration

Config is stored in `~/.pressa/config.json`:

```json
{
  "api_key": "pressa_xxxx",
  "api_url": "https://api.pressa.dev"
}
```

## Development

```bash
cd cli
npm install
npm run build
npm run dev    # watch mode
```

## License

MIT
npm package: @pressa/mcp
Description: MCP server for Pressa — LaTeX to PDF compilation service
Author: Pressa
Latest version: 0.1.1

# @pressa/mcp

MCP (Model Context Protocol) server for [Pressa](https://pressa.dev) - a LaTeX-to-PDF compilation service. This server lets AI assistants compile LaTeX documents and check API usage through a standardized interface.

## Setup

Add this to your MCP client configuration (e.g. Claude Desktop, Cursor):

```json
{
  "mcpServers": {
    "pressa": {
      "command": "npx",
      "args": ["-y", "@pressa/mcp"],
      "env": {
        "PRESSA_API_KEY": "pressa_your_key_here"
      }
    }
  }
}
```

## Environment Variables

| Variable | Required | Default | Description |
|----------|----------|---------|-------------|
| `PRESSA_API_KEY` | Yes | - | Your Pressa API key (starts with `pressa_`) |
| `PRESSA_API_URL` | No | `https://api.pressa.dev` | API base URL |

## Tools

### `compile`

Compile LaTeX source code into a PDF.

**Input:**

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `latex` | string | Yes | LaTeX source code |
| `compiler` | string | No | `"pdflatex"`, `"xelatex"`, or `"lualatex"` |

**Output (success):**

```json
{
  "job_id": "ffc2bd62-3b67-45d6-be14-b529c4b9489f",
  "pdf_url": "https://api.pressa.dev/api/v1/pdfs/ffc2bd62...?sig=xxx&exp=xxx",
  "expires_at": "2026-04-09T20:44:55Z",
  "pages": 1,
  "compilation_time_ms": 359,
  "usage": {
    "plan": "free",
    "compilations_this_month": 9,
    "monthly_limit": 100
  }
}
```

**Output (error):** Compilation log and error line number.

### `usage`

Get current API usage statistics.

**Input:** None.

**Output:**

```json
{
  "user": {
    "email": "user@example.com",
    "username": "user",
    "plan": "free"
  },
  "usage": {
    "compilations_this_month": 9,
    "monthly_limit": 100,
    "remaining": 91,
    "resets_at": "2026-04-30T23:59:59Z"
  },
  "api_key": {
    "prefix": "pressa_a",
    "name": "my-key",
    "total_requests": 15,
    "last_used_at": "2026-04-08T20:44:55Z"
  }
}
```

## Development

```bash
npm install
npm run build
npm start
```

## License

MIT
npm package: @pressbooks/reorderable-multiselect
Description: Webcomponent pressbooks-reorderable-multiselect following open-wc recommendations
Author: Pressbooks
Latest version: 0.0.4

# \<pressbooks-reorderable-multiselect>

[![Latest version](https://badgen.net/npm/v/@pressbooks/reorderable-multiselect)](https://npmjs.com/package/@pressbooks/reorderable-multiselect) [![MIT license](https://badgen.net/npm/license/@pressbooks/reorderable-multiselect)](https://github.com/pressbooks/reorderable-multiselect/tree/main/LICENSE) 

A web component which allows users to select multiple items from a list and customize the order in which they appear, built with [Lit](https://lit.dev). This web
component follows the [open-wc](https://github.com/open-wc/open-wc) recommendations.

It is largely based on the [ARIA Listbox](https://www.w3.org/WAI/ARIA/apg/patterns/listbox/) pattern.

## Installation

```bash
npm i @pressbooks/reorderable-multiselect
```

## Usage

TODO.

### Styling

Because this web component uses the Shadow Dom, styling is limited to modification via CSS custom properties. However,
there are plenty to choose from.

## Linting and formatting

To scan the project for linting and formatting errors, run

```bash
npm run lint
```

To automatically fix linting and formatting errors, run

```bash
npm run format
```

## Testing with Web Test Runner

To execute a single test run:

```bash
npm run test
```

To run the tests in interactive watch mode run:

```bash
npm run test:watch
```

## Tooling configs

For most of the tools, the configuration is in the `package.json` to minimize 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 `web-dev-server`

```bash
npm start
```

To run a local development server that serves the basic demo located in `demo/index.html`

## Publishing to NPM

As this is a scoped package it must be published by someone within the Pressbooks NPM organization and must use the `--access public` flag:

```bash
npm publish --access public
```
npm package: @pressdocs/lang-js
Description: Pressdocs documentation provider for JavaScript
Author: eFrane
Latest version: 0.1.4

# @pressdocs/lang-js -

> JsDoc Language Provider for pressdocs

Add this to your VuePress + pressdocs setup to include
JsDoc-based code documentation.

```bash
npm i -D @pressdocs/lang-js
```
npm package: @pressflow/tracker
Description: Lightweight page view tracking for Pressflow
Latest version: 0.1.0

# @pressflow/tracker

Lightweight page view tracking for [Pressflow](https://pressflow.io) blogs. Under 1 KB gzipped. Uses `navigator.sendBeacon()` with `fetch` keepalive fallback for reliable delivery.

## Installation

### Script tag (recommended)

Add this snippet to your article pages. No build step required.

```html
<script
  src="https://cdn.pressflow.io/tracker/v1/snippet.js"
  data-api-url="https://api.pressflow.io"
  data-api-key="pk_..."
  data-article-id="article-uuid"
  defer
></script>
```

### npm

```bash
npm install @pressflow/tracker
```

## Quick Start

```typescript
import { Tracker } from "@pressflow/tracker"

const tracker = new Tracker({
  baseUrl: "https://api.pressflow.io",
  apiKey: "pk_...",
  articleId: "article-uuid", // auto-tracks on construction
})
```

Or track manually:

```typescript
const tracker = new Tracker({
  baseUrl: "https://api.pressflow.io",
  apiKey: "pk_...",
})

tracker.trackPageView("article-uuid")
```

## API Reference

### `new Tracker(config)`

Creates a tracker instance. If `articleId` is provided, a page view is tracked immediately.

### `trackPageView(articleId)`

Sends a page view event for the given article. Each tracker instance only fires once — subsequent calls are ignored.

| Parameter   | Type     | Required | Description              |
| ----------- | -------- | -------- | ------------------------ |
| `articleId` | `string` | Yes      | The article's unique ID  |

## Configuration

### `TrackerConfig`

| Parameter   | Type     | Required | Default | Description                    |
| ----------- | -------- | -------- | ------- | ------------------------------ |
| `baseUrl`   | `string` | Yes      | -       | Pressflow API base URL         |
| `apiKey`    | `string` | Yes      | -       | Your public API key            |
| `articleId` | `string` | No       | -       | Auto-track this article on init |

### Script tag attributes

| Attribute         | Required | Description              |
| ----------------- | -------- | ------------------------ |
| `data-api-url`    | Yes      | Pressflow API base URL   |
| `data-api-key`    | Yes      | Your public API key      |
| `data-article-id` | Yes      | The article's unique ID  |

## How it works

1. On construction (or when `trackPageView` is called), the tracker sends a single event containing the article ID, page referrer, and user agent.
2. It first attempts `navigator.sendBeacon()` for non-blocking delivery that survives page unloads.
3. If `sendBeacon` is unavailable or fails, it falls back to `fetch` with `keepalive: true`.
4. Each tracker instance tracks at most one page view to prevent duplicates.

## GDPR

The tracker collects only the page referrer and user agent string — no cookies, no fingerprinting, no personal data. It is compatible with cookie-free analytics. If your site requires user consent for any analytics, gate the script or `Tracker` instantiation behind your consent mechanism.

## License

MIT