open-index/open-npm huggingface dataset:
npm package: @salthq/admin-component-lib
Description: A library of admin components written with Vite, Vue3, Storybook, TypeScript and TailwindCSS
Author: Advantage Learning Technologies
Latest version: 1.1.26

# Salt HQ admin component library

## Stack

A library of admin components written with Vite, Vue3, Storybook, TypeScript and TailwindCSS

## Install

Run: `npm i @salthq/admin-component-lib`

## Local component usage

You can include any of the components locally by adding:

```
<script setup lang="ts">
import { SltAdminButton } from "@salthq/admin-component-lib";
</script>

<template>
    <slt-admin-button />
</template>
```

## Package management

### Installation

- Clone repository to your local machine
- Install dependecies: `npm install`

## Run Storybook for HMR development

- `npm run storybook`

## Run tests

- `npm run test`

// TODO
Re-write all the tests to use Vitest expect instead of external 'chai' `assert` https://vitest.dev/api/#expect

## Update changelog

- Add new version and changes to `changelog.md`

## Build prod distribution

- `npm run build`

## Publish to npm

- Make sure version in `package.json` is updated (incremented up)
- Commit changes and push to main
- Create a release `git tag -a 1.0.1 -m "Release version 1.0.1" && git push origin 1.0.1`
- `npm run build`
- Log in to NPM first by running `npm login` and inserting your credentials
- Publish package `npm publish --access=public`
npm package: @saltie2193/scriptable-util
Description: Utils for Scriptable on iOS
Author: saltie2193
Latest version: 1.0.0

# scriptable-util

Simple library containing utilities to simplify writing of scripts for [Scriptable](https://scriptable.app).

Currently provides a wrapper around [`FileManager`]((https://docs.scriptable.app/filemanager/)) of scriptable, as well as a the class `DataResponse` allowing for easier handling of responses of data requests.
npm package: @saltify/milky-generator
Description: Milky codegen CLI
Author: SaltifyDev
Latest version: 0.3.1
Deprecated: Published with a new package name. Please use 'milkygen' instead.

# @saltify/milky-generator

Milky 代码生成 CLI，用于基于 Milky IR 生成不同目标格式的规范文件。

## 安装

```bash
npm install -g @saltify/milky-generator
```

安装后可直接使用命令：

```bash
milkygen
```

## 命令

### 生成内容

> 别名：`g`, `gen`

```
milkygen generate <generator> [--output <file>] [--version <version>]
```

示例：

```bash
milkygen generate openapi
milkygen generate json-schema -o ./dist/schema.json
milkygen generate typescript/zod -version latest --output ./generated/schema.ts
milkygen generate rust/serde --version 1.2.1
```

参数说明：

- `--output`, `-o`: 输出文件路径；若未提供，输出到标准输出。
- `--version`, `-v`: 指定使用的 Milky IR 版本，支持以下值：
  - `latest`: 默认值，使用 npm `latest` 标签对应版本的协议定义。
  - 具体版本号: **只能使用 `1.2.1` 及以上版本**，因为协议定义在 `1.2.1` 版本中才正式发布。
  - `local`: 使用当前包依赖中的本地协议定义。不建议使用，因为可能与发布版本不一致。
- `--cdn`: 指定从哪个 CDN 获取协议定义，默认为 `unpkg`。可用值请使用 `milkygen list-cdns` 命令查看。

### 查看可用 generator

> 别名：`l`

```
milkygen list
```

### 查看可用 CDN

```
milkygen list-cdns
```

### 查看 CLI 版本

```
milkygen version
```

注意这里的 version 是指 milkygen CLI 的版本，而不是 Milky IR 协议的版本。Milky IR 协议版本需要通过 `--version` 参数指定，具体说明见上文。
npm package: @saltify/milky-protocol
Description: Milky protocol definition in form of IR
Author: SaltifyDev
Latest version: 1.2.2

# @saltify/milky-protocol

这是 Milky 协议的定义包，包含了以 Milky IR 形式定义的协议结构。

## 安装与使用

可以通过 npm 等包管理工具安装：

```bash
npm install @saltify/milky-protocol
```

安装后，可以在项目中导入协议定义：

```typescript
import ir from '@saltify/milky-protocol';
```

此外，也可以直接通过 CDN 获取 JSON 格式的协议定义，例如：

```
https://unpkg.com/@saltify/milky-protocol@latest/dist/protocol.json
https://esm.sh/@saltify/milky-protocol@latest/dist/protocol.json
https://cdn.jsdelivr.net/npm/@saltify/milky-protocol@latest/dist/protocol.json
```

## Milky IR 介绍

Milky IR 是 Milky 提供的一种中间表示（Intermediate Representation），主要目的是以更少的歧义、更稳定的结构向代码生成器提供一份足够简洁的类型定义模型。一个生成器即使不理解完整的 OpenAPI 或 JSON Schema 规范，也能通过 Milky IR 来生成可用的模型和接口代码。

Milky IR 主要包含两大部分：

- 公共结构体（Common Structs）：定义了协议中使用的各种数据结构，包括普通结构体和联合类型。
- API 分类（API Categories）：按照功能划分的 API 列表，每个类别下包含相关的 API 定义。

以下是部分核心概念的介绍，并没有覆盖 IR 中的所有概念，完整类型定义可参考源代码中的 `types.ts` 文件。

### 字段（Field）

字段本身只保留实现层最常用的信息，例如：

- 字段类型
- 字段名
- 字段描述
- 是否为数组
- 是否可选
- 默认值

其中字段类型有三种：

- `scalar`：基础标量类型，如 `int32`、`int64`、`string`、`bool`
- `enum`：枚举值列表
- `ref`：对其他公共结构体的引用

此外还有字段数据类型（Data Type）的概念，主要用于标记某个字段属于特殊的数据类型。目前 Milky IR 定义了如下数据类型：

- `uin`：一种特殊的 `int64`，用于表示 QQ 号或群号。

### 联合类型（Union Struct）

联合类型往往是代码生成中最麻烦的部分之一，也是 Milky IR 相比通用描述格式更有针对性的地方。Milky IR 将联合类型分为两类：

- `plain`：当一个联合类型的各个分支本身就是彼此独立的结构时，IR 会将其表示为 `plain` union。每个分支都有自己的判别值和字段集合，适合直接映射为不同语言中的枚举变体、sealed class、tagged union 等形式。典型的例子是 `GroupNotification`。
- `withData`：当一个联合类型具有稳定的公共字段，并通过 `data` 字段承载具体分支内容时，IR 会将其表示为 `withData` union。此时公共字段会单独提取为 `baseFields`，各个分支则以派生类型的形式记录。典型的例子是 `IncomingSegment` 和 `Event`，它们沿用了 OneBot 11 的设计。
npm package: @saltify/milky-types
Description: Type definitions for Milky protocol
Author: SaltifyDev
Latest version: 1.2.2

# @saltify/milky-types

这是 Milky 协议的 TypeScript 类型定义包，使用 [Zod](https://zod.dev/) 进行运行时类型验证。

## 安装

```bash
npm install @saltify/milky-types
```

## 使用方法

### 进行运行时类型验证

```typescript
import { FriendEntity } from '@saltify/milky-types';

const friend1 = FriendEntity.parse({
  user_id: 123456789,
  nickname: 'Alice',
  sex: 'female',
  qid: 'Saltify',
  remark: 'Best friend',
  category: {
    id: 1,
    name: 'Close Friends',
  },
}); // 成功解析，friend1 的类型为 FriendEntity

const friend2 = FriendEntity.parse({
  user_id: 'not a number',
  nickname: 'Bob',
}); // 解析失败，抛出 ZodError 错误
```

### 获取 TypeScript 类型定义

```typescript
import { FriendEntity } from '@saltify/milky-types';

const friend1: FriendEntity = {
  user_id: 123456789,
  nickname: 'Alice',
  sex: 'female',
  qid: 'Saltify',
  remark: 'Best friend',
  category: {
    id: 1,
    name: 'Close Friends',
  },
}; // friend1 的类型为 FriendEntity

const friend2: FriendEntity = {
  user_id: 'not a number',
  nickname: 'Bob',
}; // TypeScript 编译错误，user_id 应为 number 类型，并且缺少 sex、qid、remark 和 category 字段
```
npm package: @salto-io/jest-extended
Description: Additional Jest matchers
Author: Matt Phillips
Latest version: 4.0.3

<div align="center">
  <h1>jest-extended</h1>

🃏💪

Additional Jest matchers

</div>

<hr />

[![Build Status](https://img.shields.io/github/actions/workflow/status/jest-community/jest-extended/ci.yaml?style=flat-square)](https://github.com/jest-community/jest-extended/actions/workflows/ci.yaml)
[![Code Coverage](https://img.shields.io/codecov/c/github/jest-community/jest-extended.svg?style=flat-square)](https://codecov.io/github/jest-community/jest-extended)
[![version](https://img.shields.io/npm/v/jest-extended.svg?style=flat-square)](https://www.npmjs.com/package/jest-extended)
[![downloads](https://img.shields.io/npm/dm/jest-extended.svg?style=flat-square)](http://npm-stat.com/charts.html?package=jest-extended&from=2017-09-14)
[![MIT License](https://img.shields.io/npm/l/jest-extended.svg?style=flat-square)](https://github.com/jest-community/jest-extended/blob/main/LICENSE)
[![PRs Welcome](https://img.shields.io/badge/PRs-welcome-brightgreen.svg?style=flat-square)](./CONTRIBUTING.md)
[![Examples](https://img.shields.io/badge/%F0%9F%92%A1-examples-ff615b.svg?style=flat-square)](https://github.com/jest-community/jest-extended/tree/main/examples)

## Problem

Jest is an amazing test runner and has some awesome assertion APIs built in by default. However, there are times when
having more specific matchers (assertions) would be far more convenient.

## Solution

jest-extended aims to add additional matchers to Jest's default ones making it easy to test everything 🙌

## Contributing

If you've come here to help contribute - Thanks! Take a look at the [contributing](/CONTRIBUTING.md) docs as a way of getting started.

## Installation

See the [Installation Guide](https://jest-extended.jestcommunity.dev/docs/getting-started/install) on Jest Extended documentation site.

## Setup

See the [Setup instructions](https://jest-extended.jestcommunity.dev/docs/getting-started/setup) on Jest Extended documentation site.

## Matchers

See all available [matchers and interactive repl](https://jest-extended.jestcommunity.dev/docs/matchers) on Jest Extended documentation site.

## LICENSE

[MIT](/LICENSE)
npm package: @salto-io/jsforce
Description: Fork of jsforce with some modifications
Latest version: 1.9.5

# jsforce 

Salesforce API Library for JavaScript applications (both on web browser and Node.js)

[![CircleCI](https://circleci.com/gh/jsforce/jsforce.svg?style=svg)](https://circleci.com/gh/jsforce/jsforce)

## Overview

JSforce (f.k.a. Node-Salesforce) is an isomorphic JavaScript Library utilizing Salesforce's API: It works both in the browser and with Node.js.

It capsulates the access to various APIs provided by Salesforce in asynchronous JavaScript function calls.

It also has command line interface (CLI) which gives interactive console (REPL), so you can learn the usage without hassle.

Supported Salesforce APIs are the following:

- REST API (SOQL, SOSL, describe, etc.)
- Apex REST
- Analytics API
- Bulk API
- Chatter API
- Metadata API
- SOAP API
- Streaming API
- Tooling API

## Documentation

See documentation in http://jsforce.github.io/ .

## Releases

See [Releases](https://github.com/jsforce/jsforce/releases).

## License

See [license](LICENSE) (MIT License).

## Authors

- Shinichi Tomita <shinichi.tomita@gmail.com>


## Notes

If you have any questions first file it on [issues](https://github.com/jsforce/jsforce/issues) before contacting authors via e-mail.

## Tests

In order to run tests you will need a [Salesforce Developer Org](https://developer.salesforce.com/signup)

You will also need to install the JsforceTestSuite package, which can be done by running:

    SF_USERNAME=myusername SF_PASSWORD=password+securityToken ./test/bin/org-setup

You may need to run this more then once if you encounter timeouts or dropped connections/

Finally, to run the tests simply do:

    SF_USERNAME=myusername SF_PASSWORD=password+securityToken npm run test:node

    SF_USERNAME=myusername SF_PASSWORD=password+securityToken npm run test:browser

## Contributions

Your contributions are welcome: both by reporting issues on [GitHub issues](https://github.com/jsforce/jsforce/issues) or pull-requesting patches.

If you want to implement any additional features, to be added to JSforce to our master branch, which may or may not be merged please first check current [opening issues](https://github.com/jsforce/jsforce/issues?q=is%3Aopen) with milestones and confirm whether the feature is on road map or not.

If your feature implementation is brand-new or fixing unsupposed bugs in the library's test cases, please include addtional test codes in the `test/` directory.