open-index/open-npm huggingface dataset:
npm package: @haklex/rich-static-renderer
Description: Headless SSR engine for Lexical rich content
Latest version: 0.0.104

# @haklex/rich-static-renderer

SSR-ready renderer engine for Lexical rich content. Renders Lexical editor state JSON to React without loading the full editor runtime.

## Installation

```bash
pnpm add @haklex/rich-static-renderer
```

## Peer Dependencies

This package depends on `@lexical/code-core` (Lexical 0.42+ code blocks, no Prism). Add `@lexical/code-core` yourself only if your app imports it directly.

| Package              | Version   |
| -------------------- | --------- |
| `@lexical/extension` | `^0.42.0` |
| `@lexical/link`      | `^0.42.0` |
| `@lexical/list`      | `^0.42.0` |
| `@lexical/rich-text` | `^0.42.0` |
| `@lexical/table`     | `^0.42.0` |
| `lexical`            | `^0.42.0` |
| `react`              | `>=19`    |
| `react-dom`          | `>=19`    |

## Usage

```tsx
import { RichRenderer } from '@haklex/rich-static-renderer';
import '@haklex/rich-editor/style.css';

<RichRenderer value={editorState} variant="article" theme="light" />;
```

The `value` prop accepts a Lexical `SerializedEditorState` JSON object. The renderer parses it into React elements without instantiating a Lexical editor, making it suitable for SSR and static rendering.

## Exports

### Components

| Export         | Description                    |
| -------------- | ------------------------------ |
| `RichRenderer` | Main static renderer component |

### Types

| Export                | Description                              |
| --------------------- | ---------------------------------------- |
| `RichRendererProps`   | Props for `RichRenderer`                 |
| `BuiltinNodeRenderer` | Type for builtin node renderer functions |

## Part of Haklex

This package is part of the [Haklex](../../README.md) rich editor ecosystem.

## License

MIT
npm package: @haklex/rich-style-token
Description: Style tokens and CSS variables for haklex rich editor
Latest version: 0.0.104

# @haklex/rich-style-token

Design tokens, CSS variables, and variant presets for the Haklex rich editor theme system.

## Installation

```bash
pnpm add @haklex/rich-style-token
```

## Peer Dependencies

| Package | Version |
| --- | --- |
| `react` | `>=19` |

## Usage

```tsx
import { createThemeStyle, articleTheme, vars } from '@haklex/rich-style-token'
import { PortalThemeProvider } from '@haklex/rich-style-token'

// Generate inline style object from a theme
const style = createThemeStyle(articleTheme)

// Use CSS variables in your styles
// vars.fontSize, vars.lineHeight, vars.fontFamily, etc.

// Provide portal theme context for overlays
<PortalThemeProvider theme="light" variant="article">
  {children}
</PortalThemeProvider>
```

## Exports

### Theme Construction

| Export | Description |
| --- | --- |
| `createThemeStyle(tokens)` | Generate a CSS variable style object from theme tokens |

### Context Providers

| Export | Description |
| --- | --- |
| `PortalContainerProvider` | Provide a custom portal container element |
| `usePortalContainer()` | Access the portal container element |
| `PortalThemeProvider` | Provide theme context for portaled overlays |
| `PortalThemeWrapper` | Wrapper element that applies theme variables |
| `usePortalTheme()` | Access the current portal theme |

### Design Tokens

| Export | Description |
| --- | --- |
| `articleLayout` | Layout tokens for the `article` variant (sans-serif, 16px) |
| `noteLayout` | Layout tokens for the `note` variant (CJK serif, 16px) |
| `commentLayout` | Layout tokens for the `comment` variant (sans-serif, 14px) |
| `darkColors` | Color tokens for dark mode |
| `lightArticleColors` | Color tokens for light article/note mode |
| `lightCommentColors` | Color tokens for light comment mode |
| `fonts` | Font family definitions |

### Theme Objects

| Export | Description |
| --- | --- |
| `articleTheme` | Complete theme for the `article` variant |
| `noteTheme` | Complete theme for the `note` variant |
| `commentTheme` | Complete theme for the `comment` variant |
| `vars` | Typed CSS variable references (use in Vanilla Extract styles) |

### Types

| Export | Description |
| --- | --- |
| `ThemeTokens` | Shape of a complete theme token set |
| `PortalTheme` | Portal theme descriptor |

### Sub-path Exports

| Import Path | Description |
| --- | --- |
| `@haklex/rich-style-token` | All tokens, themes, providers, and utilities |
| `@haklex/rich-style-token/styles` | Vanilla Extract style definitions |

## Part of Haklex

This package is part of the [Haklex](../../README.md) rich editor ecosystem.

## License

MIT
npm package: @hakobu/hakobu-fetch
Description: Compiles and stores patched Node.js base binaries for Hakobu
Latest version: 1.0.1

# @hakobu/hakobu-fetch

Fetches or builds patched Node.js binaries used by [Hakobu](https://github.com/hakobujs/hakobu) to produce standalone executables.

## Supported Targets

Hakobu targets Node 24.x LTS. The following base binaries are published:

| Platform | Architecture | Tier | Status |
|---|---|---|---|
| linux | x64 | 1 | Active |
| linux | arm64 | 1 | Active |
| win | x64 | 1 | Active |
| macos | arm64 | 1 | Active |
| macos | x64 | 2 | Active |
| linuxstatic | x64 | 2 | Active |
| win | arm64 | 2 | Active |

See the [Target Policy](https://github.com/hakobujs/hakobu/blob/main/docs/target-policy.md) for tier definitions and build strategies.

## Usage

This package is used internally by `@hakobu/hakobu`. You typically don't need to install it directly.

```bash
# Hakobu installs this automatically
npm install @hakobu/hakobu
```

If you need to pre-fetch a base binary (e.g., for offline/air-gapped builds):

```bash
npx @hakobu/hakobu-fetch --node-range node24 --platform linux --arch x64
```

## Environment Variables

| Variable | Description |
|---|---|
| `PKG_CACHE_PATH` | Directory to cache base binaries. Default: `~/.pkg-cache` |
| `PKG_BUILD_PATH` | Directory to clone and build Node.js binaries. Default: system temp |
| `PKG_NODE_PATH` | Custom path to a local Node.js binary to use instead of fetching |
| `PKG_IGNORE_TAG` | Ignore tag folder when checking local binary path |
| `HTTPS_PROXY` | HTTPS proxy for fetching binaries |
| `HTTP_PROXY` | HTTP proxy for fetching binaries |
| `MAKE_JOB_COUNT` | Parallel jobs for building binaries (passed to `make -j`). Default: CPU count |

## Security

Base binaries are compiled by [GitHub Actions](https://github.com/hakobujs/hakobu/actions) with transparent, auditable workflows. Binary checksums are recorded in [expected-shas.json](./lib/expected-shas.json) and verified at fetch time.

## License

MIT
npm package: @hakochest/ciallo
Description: A simple NPM package for practicing package publishing and maintenance. Outputs 'Ciallo～(∠・ω< )⌒☆' to the console.
Author: HakoChest
Latest version: 0.721.0


# @hakochest/ciallo

一个简单的 NPM 包，用于练习包的发布与维护。输出 "Ciallo～(∠・ω< )⌒☆" 到控制台。

## 安装

```bash
npm install @hakochest/ciallo
```

## 使用

### CommonJS

```javascript
const ciallo = require('@hakochest/ciallo');
ciallo(); // 输出: Ciallo～(∠・ω< )⌒☆
```

### ES Module

```js
import ciallo from '@hakochest/ciallo';
ciallo(); // 输出: Ciallo～(∠・ω< )⌒☆
```

## API

### ciallo()

调用后在控制台输出 "Ciallo～(∠・ω< )⌒☆"。

#### 示例

```js
ciallo(); // 输出: Ciallo～(∠・ω< )⌒☆
```

## 特性

- 极简易用
- 支持 TypeScript
- 兼容 CommonJS 和 ESM

## 贡献

欢迎 PR 和 issue！如有建议或问题，欢迎提交。

## 许可证

MIT
npm package: @hakochest/ciallo-wasm
Description: Ciallo with WebAssembly
Latest version: 0.7.210

# @hakochest/ciallo_wasm

![Ciallo～(∠・ω< )⌒☆](CialloWasm.png)

[![crates.io](https://img.shields.io/crates/v/ciallo_wasm.svg)](https://crates.io/crates/ciallo_wasm)
[![npm](https://img.shields.io/npm/v/@hakochest/ciallo_wasm.svg)](https://www.npmjs.com/package/@hakochest/ciallo-wasm)

[中文](README.md) | [English](README_EN.md)

一个将字符串 `Ciallo～(∠・ω< )⌒☆` 打印到浏览器控制台的 WebAssembly 库。

## 安装

使用你喜欢的包管理器安装：

```bash
# npm
npm install @hakochest/ciallo-wasm

# yarn
yarn add @hakochest/ciallo-wasm

# pnpm
pnpm add @hakochest/ciallo-wasm
```

## 用法

```javascript
import { ciallo } from '@hakochest/ciallo-wasm';

ciallo();
```

在浏览器的开发者工具控制台中，你将看到：

```console
Ciallo～(∠・ω< )⌒☆
```

## 测试

仓库根目录的 `test/` 目录包含两个测试/示例：

- `test/node/`：基于 Node 的示例 — 由于 NodeJS 当前对 WebAssembly 的一些支持限制，该示例暂时不太适配（需要额外的 Node-WASM 配置或运行时支持）。
- `test/vue/`：基于 Vue 的示例 — 已完美适配，可直接作为在浏览器中通过打包加载本库的参考。

如果要运行 `vue` 示例，请进入 `test/vue` 并按照该目录内的说明使用 npm/yarn 安装依赖并启动开发服务器。

## Rust 包 (Crate)

此库使用 Rust 和 `wasm-pack` 构建。如果你想在 Rust 项目中使用它，请查看 [ciallo_wasm on Crates.io](https://crates.io/crates/ciallo_wasm)。
npm package: @hakonhagen/npm-test-package
Description: Made with create-react-library
Author: hakhag
Latest version: 1.0.1

# npm-test-package

> Made with create-react-library

[![NPM](https://img.shields.io/npm/v/npm-test-package.svg)](https://www.npmjs.com/package/npm-test-package) [![JavaScript Style Guide](https://img.shields.io/badge/code_style-standard-brightgreen.svg)](https://standardjs.com)

## Install

```bash
npm install --save npm-test-package
```

## Usage

```tsx
import React, { Component } from 'react'

import MyComponent from 'npm-test-package'
import 'npm-test-package/dist/index.css'

class Example extends Component {
  render() {
    return <MyComponent />
  }
}
```

## License

MIT © [hakhag](https://github.com/hakhag)
npm package: @haku530/pixivapi
Description: null
Latest version: 1.0.1

# @haku530/koishi-plugin-pixivapi

[![npm](https://img.shields.io/npm/v/@haku530/koishi-plugin-pixivapi?style=flat-square)](https://www.npmjs.com/package/@haku530/koishi-plugin-pixivapi)

null
npm package: @hakui/eslint-config
Description: A collection of ESLint configurations for various environments.
Latest version: 0.0.5

# `@hakui/eslint-config`

A collection of ESLint configurations for various environments.

## Installation

To install the package, run:

```sh
npm install @hakui/eslint-config --save-dev
```

or

```sh
yarn add @hakui/eslint-config --dev
```

## Usage

You can use the configurations in your ESLint setup by importing them in your `.eslint.config.mjs` or equivalent configuration file.

### Next.js

```js
import { config } from '@hakui/eslint-config/next-js';

/** @type {import('eslint').Linter.Config} */
export default config;
```

### React

```js
import { config } from '@hakui/eslint-config/react-internal';

/** @type {import("eslint").Linter.Config} */
export default config;
```

### Vite

```js
import { config } from '@hakui/eslint-config/vite';

/** @type {import("eslint").Linter.Config} */
export default config;
```

### Custom

You can also extend the configurations to suit your needs. For example:

```js
import { config as baseConfig } from '@hakui/eslint-config/base';

/** @type {import('eslint').Linter.Config} */
export default [
  ...baseConfig,
  {
    rules: {
      // Add your custom rules here
    },
  },
];
```