@renkosky/lark-fe-skills 0.1.0 → 0.1.2

package/README.md

@@ -1,32 +1,56 @@
 # Lark FE Skills
 
+[![npm version](https://img.shields.io/npm/v/@renkosky/lark-fe-skills.svg)](https://www.npmjs.com/package/@renkosky/lark-fe-skills) [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](./LICENSE) [![Codex Skills](https://img.shields.io/badge/Codex-Skills-111827.svg)](https://github.com/openai/codex) [![Lark CLI](https://img.shields.io/badge/Lark-CLI-00A6FF.svg)](https://github.com/larksuite/cli/tree/main)
+
 English | [中文](#中文)
 
+Lark/Feishu based Codex skills for frontend requirement planning.
+
+[Install](#install) · [Prerequisites](#prerequisites) · [CLI](#cli) · [Roadmap](#roadmap) · [中文](#中文)
+
 ## English
 
-`@renkosky/lark-fe-skills` packages Codex skills for Lark-based frontend requirement workflows.
+## ✨ What is this?
+
+`@renkosky/lark-fe-skills` packages Codex skills for Lark-based frontend workflows.
 
-The first packaged skill is `lark-fe-task`, which reads a Lark/Feishu requirement document and generates a frontend task breakdown Markdown file.
+The first packaged workflow includes `prd-fe-task` for task breakdowns and `prd-fe-schedule` for Lark Base schedule dry-runs.
 
-### Install
+## 🚀 Install
+
+1. Install the package:
 
 ```bash
 npm install -g @renkosky/lark-fe-skills
-lark-fe-skills install lark-fe-task
 ```
 
-Then use the installed skill from Codex:
+2. Install the skill:
+
+```bash
+lark-fe-skills install prd-fe-task
+```
+
+3. Restart Codex or open a new Codex session.
+
+PATH fallback:
+
+```bash
+npm exec --package=@renkosky/lark-fe-skills -- lark-fe-skills install prd-fe-task
+```
+
+Use it in Codex:
 
 ```text
-[$lark-fe-task](~/.codex/skills/lark-fe-task/SKILL.md) +config
-[$lark-fe-task](~/.codex/skills/lark-fe-task/SKILL.md) +plan <Lark document title, URL, or token>
+[$prd-fe-task](~/.codex/skills/prd-fe-task/SKILL.md) +config
+[$prd-fe-task](~/.codex/skills/prd-fe-task/SKILL.md) +plan <Lark document title, URL, or token>
 ```
 
-### Prerequisites
+## 🧰 Prerequisites
 
-Install and configure `lark-cli` before using the skill:
+Install Node.js and configure `lark-cli` first:
 
 ```bash
+npm --version
 npm install -g @larksuite/cli
 lark-cli config init
 lark-cli auth login --recommend
@@ -34,20 +58,36 @@ lark-cli auth login --recommend
 
 Official lark-cli documentation: <https://github.com/larksuite/cli/tree/main>
 
-### CLI
+## 🖥️ CLI
 
 ```bash
 lark-fe-skills list
 lark-fe-skills path
-lark-fe-skills path lark-fe-task
-lark-fe-skills install lark-fe-task
+lark-fe-skills path prd-fe-task
+lark-fe-skills path prd-fe-schedule
+lark-fe-skills install prd-fe-task
+lark-fe-skills install prd-fe-schedule
+lark-fe-skills uninstall prd-fe-task
+lark-fe-skills uninstall prd-fe-schedule
+lark-fe-skills uninstall lark-fe-task
 ```
 
-### Packaged Skills
+## 📦 Packaged Skills
+
+| Skill | Description |
+| --- | --- |
+| `prd-fe-task` | Turn Lark/Feishu requirement documents into concrete frontend task breakdowns. |
+| `prd-fe-schedule` | Preview Lark Base schedule records from generated frontend task Markdown. |
 
-- `lark-fe-task`: turn Lark/Feishu requirement documents into concrete frontend task breakdowns.
+## 📝 Notes
 
-### Roadmap
+- npm installation and Codex skill installation are separate steps.
+- This package installs skills to `~/.codex/skills`.
+- Use `lark-fe-skills uninstall prd-fe-task` to reset local Codex skill installation for first-run testing.
+- Use `lark-fe-skills uninstall lark-fe-task` to remove the legacy install directory.
+- Existing Lark skills may live under `~/.agents/skills`; that is a different source.
+
+## 🗺️ Roadmap
 
 - [x] Phase 1: Generate frontend task breakdown Markdown from Lark requirement documents.
   - [x] Configure repository root, frontend project paths, and output directory.
@@ -56,11 +96,14 @@ lark-fe-skills install lark-fe-task
   - [x] Inspect configured frontend project paths lightly for code-location clues.
   - [x] Generate ignored Markdown task files under the configured output directory.
 - [ ] Phase 2: Create Lark schedule tasks from generated frontend task Markdown.
-  - [ ] Accept a Lark schedule Base URL or title, then read its table schema before mapping fields.
-  - [ ] Map Markdown tasks into schedule fields such as task name, task description, task status, start time, and end time.
-  - [ ] Read custom task status options from the Base instead of inventing status tags.
-  - [ ] First version should be dry-run only and show the records that would be created without modifying Lark.
-  - [ ] A later version can add user confirmation and then create records in the schedule Base.
+  - [x] Add `prd-fe-schedule` dry-run skill.
+  - [x] Add YAML schedule profiles with comments for configurable fields, defaults, and record rules.
+  - [x] Accept a Lark schedule Base URL or title, then read its table schema before generating a profile.
+  - [x] Map Markdown tasks into schedule fields using profile rules instead of hard-coded company task types.
+  - [x] Configure and remember task classification rules with `+config-types`.
+  - [x] Read custom task status/type options from the Base instead of inventing tags.
+  - [x] Support dry-run previews from a profile without modifying Lark.
+  - [x] Add an explicit `+create` helper that requires confirmation/`--yes` before writing records.
 - [ ] Phase 3: Implement frontend tasks from generated Markdown.
   - [ ] Default to implementing one task at a time to keep human review small and manageable.
   - [ ] After each task, stop and report changed files, verification results, remaining tasks, mocks used, and unresolved questions.
@@ -79,29 +122,49 @@ lark-fe-skills install lark-fe-task
 
 ## 中文
 
+[安装](#安装) · [前置条件](#前置条件) · [CLI](#cli-1) · [开发规划](#开发规划) · [English](#english)
+
+## ✨ 这是什么？
+
 `@renkosky/lark-fe-skills` 用于分发基于 Lark/飞书的前端需求工作流 Codex skills。
 
-首个发布的 skill 是 `lark-fe-task`，用于读取 Lark/飞书需求文档，并生成前端任务拆分 Markdown。
+首个工作流包含 `prd-fe-task` 和 `prd-fe-schedule`：前者生成前端任务拆分，后者基于任务 Markdown 生成 Lark Base 排期 dry-run 预览。
+
+## 🚀 安装
 
-### 安装
+1. 安装 npm 包：
 
 ```bash
 npm install -g @renkosky/lark-fe-skills
-lark-fe-skills install lark-fe-task
 ```
 
-然后在 Codex 中使用已安装的 skill：
+2. 安装 skill：
+
+```bash
+lark-fe-skills install prd-fe-task
+```
+
+3. 重启 Codex 或新开一个 Codex 会话。
+
+PATH fallback：
+
+```bash
+npm exec --package=@renkosky/lark-fe-skills -- lark-fe-skills install prd-fe-task
+```
+
+在 Codex 中使用：
 
 ```text
-[$lark-fe-task](~/.codex/skills/lark-fe-task/SKILL.md) +config
-[$lark-fe-task](~/.codex/skills/lark-fe-task/SKILL.md) +plan <飞书文档标题、链接或 token>
+[$prd-fe-task](~/.codex/skills/prd-fe-task/SKILL.md) +config
+[$prd-fe-task](~/.codex/skills/prd-fe-task/SKILL.md) +plan <飞书文档标题、链接或 token>
 ```
 
-### 前置条件
+## 🧰 前置条件
 
-使用 skill 前，需要先安装并配置 `lark-cli`：
+先准备 Node.js，并安装配置 `lark-cli`：
 
 ```bash
+npm --version
 npm install -g @larksuite/cli
 lark-cli config init
 lark-cli auth login --recommend
@@ -109,20 +172,36 @@ lark-cli auth login --recommend
 
 官方 lark-cli 文档：<https://github.com/larksuite/cli/tree/main>
 
-### CLI
+## 🖥️ CLI
 
 ```bash
 lark-fe-skills list
 lark-fe-skills path
-lark-fe-skills path lark-fe-task
-lark-fe-skills install lark-fe-task
+lark-fe-skills path prd-fe-task
+lark-fe-skills path prd-fe-schedule
+lark-fe-skills install prd-fe-task
+lark-fe-skills install prd-fe-schedule
+lark-fe-skills uninstall prd-fe-task
+lark-fe-skills uninstall prd-fe-schedule
+lark-fe-skills uninstall lark-fe-task
 ```
 
-### 已包含 Skills
+## 📦 已包含 Skills
+
+| Skill | 说明 |
+| --- | --- |
+| `prd-fe-task` | 将 Lark/飞书需求文档拆解成可开发的前端任务。 |
+| `prd-fe-schedule` | 根据前端任务 Markdown 预览 Lark Base 排期记录。 |
+
+## 📝 说明
 
-- `lark-fe-task`：将 Lark/飞书需求文档拆解成可开发的前端任务。
+- npm 包安装和 Codex skill 安装是两步。
+- 本包默认安装到 `~/.codex/skills`。
+- 可以用 `lark-fe-skills uninstall prd-fe-task` 清理本地 Codex skill，方便测试首次安装流程。
+- 可以用 `lark-fe-skills uninstall lark-fe-task` 清理旧版安装目录。
+- 已有 Lark skills 可能位于 `~/.agents/skills`，这是另一类来源。
 
-### 开发规划
+## 🗺️ 开发规划
 
 - [x] Phase 1：根据 Lark 需求文档生成前端任务拆分 Markdown。
   - [x] 配置仓库根目录、前端项目路径和输出目录。
@@ -131,22 +210,25 @@ lark-fe-skills install lark-fe-task
   - [x] 轻量检查已配置前端项目路径，补充代码定位线索。
   - [x] 在已配置输出目录下生成被 git 忽略的 Markdown 任务文件。
 - [ ] Phase 2：把已生成的前端任务 Markdown 转成 Lark 排期任务。
-  - [ ] 支持用户提供 Lark 排期 Base 链接或名称，并在映射字段前读取表结构。
-  - [ ] 将 Markdown 任务映射到任务名称、任务描述、任务状态、开始时间、结束时间等排期字段。
-  - [ ] 从 Base 读取自定义任务状态选项，不臆造状态 tag。
-  - [ ] 第一版只做 dry-run 预览，展示将要创建的记录，不修改 Lark。
-  - [ ] 后续版本再增加用户确认步骤，并在确认后写入排期 Base。
+  - [x] 新增 `prd-fe-schedule` dry-run skill。
+  - [x] 新增带注释的 YAML schedule profile，用于配置字段、默认值和记录生成规则。
+  - [x] 支持用户提供 Lark 排期 Base 链接或名称，并在生成 profile 前读取表结构。
+  - [x] 根据 profile 规则映射 Markdown 任务，不再写死某家公司任务类型。
+  - [x] 支持通过 `+config-types` 配置并记住任务分类规则。
+  - [x] 从 Base 读取自定义任务状态/类型选项，不臆造 tag。
+  - [x] 支持基于 profile 的 dry-run 预览，不修改 Lark。
+  - [x] 新增显式 `+create` helper，要求确认/`--yes` 后才写入记录。
 - [ ] Phase 3：根据已生成的 Markdown 实际开发前端任务。
   - [ ] 默认一次只实现一个 Task，控制代码改动粒度，方便人工 review。
   - [ ] 每完成一个 Task 就暂停，并汇报改动文件、验证结果、剩余任务、使用的 mock 和未解决问题。
   - [ ] 只有用户明确要求继续，或明确要求一次实现多个任务时，才继续处理后续 Task。
   - [ ] 如果单个 Task 本身过大，先拆成更小的实现批次再改代码。
   - [ ] 优先复用项目里已有的接口、hooks、stores、组件、权限、i18n 和 mock 模式，再考虑新增实现。
-  - [ ] 这一阶段不做真实后端联调；接口行为不可用时，优先使用已有可复用数据或项目 mock 体系。
+  - [ ] 这一阶段不做真实后端接口对接；接口行为不可用时，优先使用已有可复用数据或项目 mock 体系。
   - [ ] 如果 API 字段、权限 key、状态枚举或核心产品行为在代码里找不到，要先询问用户，不臆造。
   - [ ] 代码改动只限制在任务 Markdown 标出的受影响项目路径和模块内。
   - [ ] 每完成一个 Task 后运行最相关的静态检查，并明确说明是否存在无关历史失败。
-- [ ] Phase 4：接口联调与后端交付文档工作流。
+- [ ] Phase 4：接口对接与后端交付文档工作流。
   - [ ] 这部分在后端接口交付格式统一前保持待定。
   - [ ] 预期方向：继续使用 Lark 作为接口交付和协作载体。
   - [ ] 实施前需要先和后端约定文档格式，包括接口地址、请求方法、请求参数、响应结构、错误码、mock 示例和负责人。

package/bin/lark-fe-skills.js

@@ -8,7 +8,11 @@ import { homedir } from 'node:os'
 const __dirname = dirname(fileURLToPath(import.meta.url))
 const packageRoot = resolve(__dirname, '..')
 const skillsRoot = join(packageRoot, 'skills')
-const availableSkills = ['lark-fe-task']
+const packagedSkills = ['prd-fe-task', 'prd-fe-schedule']
+const uninstallableSkills = [...packagedSkills, 'lark-fe-task']
+const skillRuntimeDependencies = {
+  'prd-fe-schedule': ['yaml'],
+}
 
 function usage() {
   console.log(`lark-fe-skills
@@ -17,29 +21,35 @@ Usage:
   lark-fe-skills list
   lark-fe-skills path [skill-name]
   lark-fe-skills install [skill-name]
+  lark-fe-skills uninstall [skill-name]
 
 Commands:
   list              List packaged skills.
   path              Print the package skills directory or one skill path.
   install           Copy a packaged skill to $HOME/.codex/skills.
+  uninstall         Remove an installed skill from $HOME/.codex/skills.
 
 Examples:
   lark-fe-skills list
-  lark-fe-skills path lark-fe-task
-  lark-fe-skills install lark-fe-task`)
+  lark-fe-skills path prd-fe-task
+  lark-fe-skills path prd-fe-schedule
+  lark-fe-skills install prd-fe-task
+  lark-fe-skills install prd-fe-schedule
+  lark-fe-skills uninstall prd-fe-task
+  lark-fe-skills uninstall lark-fe-task`)
 }
 
-function assertSkillName(skillName) {
-  if (!availableSkills.includes(skillName)) {
+function assertSkillName(skillName, validSkills = packagedSkills) {
+  if (!validSkills.includes(skillName)) {
     console.error(`Unknown skill: ${skillName}`)
-    console.error(`Available skills: ${availableSkills.join(', ')}`)
+    console.error(`Available skills: ${validSkills.join(', ')}`)
     process.exit(1)
   }
 }
 
 function listSkills() {
   console.log('Available skills:')
-  for (const skillName of availableSkills) {
+  for (const skillName of packagedSkills) {
     console.log(`- ${skillName}`)
   }
 }
@@ -53,7 +63,7 @@ function printPath(skillName) {
   console.log(skillsRoot)
 }
 
-function installSkill(skillName = 'lark-fe-task') {
+function installSkill(skillName = 'prd-fe-task') {
   assertSkillName(skillName)
 
   const source = join(skillsRoot, skillName)
@@ -71,9 +81,35 @@ function installSkill(skillName = 'lark-fe-task') {
   }
   cpSync(source, target, { recursive: true, force: true })
 
+  for (const dependencyName of skillRuntimeDependencies[skillName] || []) {
+    const dependencySource = join(packageRoot, 'node_modules', dependencyName)
+    const dependencyTarget = join(target, 'node_modules', dependencyName)
+    if (!existsSync(dependencySource)) {
+      console.error(`Runtime dependency not found: ${dependencyName}`)
+      console.error('Run npm install in the package before installing this skill.')
+      process.exit(1)
+    }
+    mkdirSync(dirname(dependencyTarget), { recursive: true })
+    cpSync(dependencySource, dependencyTarget, { recursive: true, force: true })
+  }
+
   console.log(`Installed ${skillName} to ${target}`)
 }
 
+function uninstallSkill(skillName = 'prd-fe-task') {
+  assertSkillName(skillName, uninstallableSkills)
+
+  const target = join(homedir(), '.codex', 'skills', skillName)
+
+  if (!existsSync(target)) {
+    console.log(`${skillName} is not installed at ${target}`)
+    return
+  }
+
+  rmSync(target, { recursive: true, force: true })
+  console.log(`Uninstalled ${skillName} from ${target}`)
+}
+
 const [command, skillName] = process.argv.slice(2)
 
 switch (command) {
@@ -86,6 +122,9 @@ switch (command) {
   case 'install':
     installSkill(skillName)
     break
+  case 'uninstall':
+    uninstallSkill(skillName)
+    break
   case undefined:
   case '-h':
   case '--help':

package/node_modules/yaml/LICENSE

@@ -0,0 +1,13 @@
+Copyright Eemeli Aro <eemeli@gmail.com>
+
+Permission to use, copy, modify, and/or distribute this software for any purpose
+with or without fee is hereby granted, provided that the above copyright notice
+and this permission notice appear in all copies.
+
+THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH
+REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND
+FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT,
+INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS
+OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER
+TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF
+THIS SOFTWARE.

package/node_modules/yaml/README.md

@@ -0,0 +1,172 @@
+# YAML <a href="https://www.npmjs.com/package/yaml"><img align="right" src="https://badge.fury.io/js/yaml.svg" title="npm package" /></a>
+
+`yaml` is a definitive library for [YAML](https://yaml.org/), the human friendly data serialization standard.
+This library:
+
+- Supports both YAML 1.1 and YAML 1.2 and all common data schemas,
+- Passes all of the [yaml-test-suite](https://github.com/yaml/yaml-test-suite) tests,
+- Can accept any string as input without throwing, parsing as much YAML out of it as it can, and
+- Supports parsing, modifying, and writing YAML comments and blank lines.
+
+The library is released under the ISC open source license, and the code is [available on GitHub](https://github.com/eemeli/yaml/).
+It has no external dependencies and runs on Node.js as well as modern browsers.
+
+For the purposes of versioning, any changes that break any of the documented endpoints or APIs will be considered semver-major breaking changes.
+Undocumented library internals may change between minor versions, and previous APIs may be deprecated (but not removed).
+
+The minimum supported TypeScript version of the included typings is 3.9;
+for use in earlier versions you may need to set `skipLibCheck: true` in your config.
+This requirement may be updated between minor versions of the library.
+
+For more information, see the project's documentation site: [**eemeli.org/yaml**](https://eemeli.org/yaml/)
+
+For build instructions and contribution guidelines, see [docs/CONTRIBUTING.md](docs/CONTRIBUTING.md).
+
+To install:
+
+```sh
+npm install yaml
+# or
+deno add jsr:@eemeli/yaml
+```
+
+**Note:** These docs are for `yaml@2`. For v1, see the [v1.10.0 tag](https://github.com/eemeli/yaml/tree/v1.10.0) for the source and [eemeli.org/yaml/v1](https://eemeli.org/yaml/v1/) for the documentation.
+
+## API Overview
+
+The API provided by `yaml` has three layers, depending on how deep you need to go: [Parse & Stringify](https://eemeli.org/yaml/#parse-amp-stringify), [Documents](https://eemeli.org/yaml/#documents), and the underlying [Lexer/Parser/Composer](https://eemeli.org/yaml/#parsing-yaml).
+The first has the simplest API and "just works", the second gets you all the bells and whistles supported by the library along with a decent [AST](https://eemeli.org/yaml/#content-nodes), and the third lets you get progressively closer to YAML source, if that's your thing.
+
+A [command-line tool](https://eemeli.org/yaml/#command-line-tool) is also included.
+
+### Parse & Stringify
+
+```js
+import { parse, stringify } from 'yaml'
+```
+
+- [`parse(str, reviver?, options?): value`](https://eemeli.org/yaml/#yaml-parse)
+- [`stringify(value, replacer?, options?): string`](https://eemeli.org/yaml/#yaml-stringify)
+
+### Documents
+
+<!-- prettier-ignore -->
+```js
+import {
+  Document,
+  isDocument,
+  parseAllDocuments,
+  parseDocument
+} from 'yaml'
+```
+
+- [`Document`](https://eemeli.org/yaml/#documents)
+  - [`constructor(value, replacer?, options?)`](https://eemeli.org/yaml/#creating-documents)
+  - [`#contents`](https://eemeli.org/yaml/#content-nodes)
+  - [`#directives`](https://eemeli.org/yaml/#stream-directives)
+  - [`#errors`](https://eemeli.org/yaml/#errors)
+  - [`#warnings`](https://eemeli.org/yaml/#errors)
+- [`isDocument(foo): boolean`](https://eemeli.org/yaml/#identifying-node-types)
+- [`parseAllDocuments(str, options?): Document[]`](https://eemeli.org/yaml/#parsing-documents)
+- [`parseDocument(str, options?): Document`](https://eemeli.org/yaml/#parsing-documents)
+
+### Content Nodes
+
+<!-- prettier-ignore -->
+```js
+import {
+  isAlias, isCollection, isMap, isNode,
+  isPair, isScalar, isSeq, Scalar,
+  visit, visitAsync, YAMLMap, YAMLSeq
+} from 'yaml'
+```
+
+- [`isAlias(foo): boolean`](https://eemeli.org/yaml/#identifying-node-types)
+- [`isCollection(foo): boolean`](https://eemeli.org/yaml/#identifying-node-types)
+- [`isMap(foo): boolean`](https://eemeli.org/yaml/#identifying-node-types)
+- [`isNode(foo): boolean`](https://eemeli.org/yaml/#identifying-node-types)
+- [`isPair(foo): boolean`](https://eemeli.org/yaml/#identifying-node-types)
+- [`isScalar(foo): boolean`](https://eemeli.org/yaml/#identifying-node-types)
+- [`isSeq(foo): boolean`](https://eemeli.org/yaml/#identifying-node-types)
+- [`new Scalar(value)`](https://eemeli.org/yaml/#scalar-values)
+- [`new YAMLMap()`](https://eemeli.org/yaml/#collections)
+- [`new YAMLSeq()`](https://eemeli.org/yaml/#collections)
+- [`doc.createAlias(node, name?): Alias`](https://eemeli.org/yaml/#creating-nodes)
+- [`doc.createNode(value, options?): Node`](https://eemeli.org/yaml/#creating-nodes)
+- [`doc.createPair(key, value): Pair`](https://eemeli.org/yaml/#creating-nodes)
+- [`visit(node, visitor)`](https://eemeli.org/yaml/#finding-and-modifying-nodes)
+- [`visitAsync(node, visitor)`](https://eemeli.org/yaml/#finding-and-modifying-nodes)
+
+### Parsing YAML
+
+```js
+import { Composer, Lexer, Parser } from 'yaml'
+```
+
+- [`new Lexer().lex(src)`](https://eemeli.org/yaml/#lexer)
+- [`new Parser(onNewLine?).parse(src)`](https://eemeli.org/yaml/#parser)
+- [`new Composer(options?).compose(tokens)`](https://eemeli.org/yaml/#composer)
+
+## YAML.parse
+
+```yaml
+# file.yml
+YAML:
+  - A human-readable data serialization language
+  - https://en.wikipedia.org/wiki/YAML
+yaml:
+  - A complete JavaScript implementation
+  - https://www.npmjs.com/package/yaml
+```
+
+```js
+import fs from 'fs'
+import YAML from 'yaml'
+
+YAML.parse('3.14159')
+// 3.14159
+
+YAML.parse('[ true, false, maybe, null ]\n')
+// [ true, false, 'maybe', null ]
+
+const file = fs.readFileSync('./file.yml', 'utf8')
+YAML.parse(file)
+// { YAML:
+//   [ 'A human-readable data serialization language',
+//     'https://en.wikipedia.org/wiki/YAML' ],
+//   yaml:
+//   [ 'A complete JavaScript implementation',
+//     'https://www.npmjs.com/package/yaml' ] }
+```
+
+## YAML.stringify
+
+```js
+import YAML from 'yaml'
+
+YAML.stringify(3.14159)
+// '3.14159\n'
+
+YAML.stringify([true, false, 'maybe', null])
+// `- true
+// - false
+// - maybe
+// - null
+// `
+
+YAML.stringify({ number: 3, plain: 'string', block: 'two\nlines\n' })
+// `number: 3
+// plain: string
+// block: |
+//   two
+//   lines
+// `
+```
+
+---
+
+Browser testing provided by:
+
+<a href="https://www.browserstack.com/open-source">
+<img width=200 src="https://eemeli.org/yaml/images/browserstack.svg" alt="BrowserStack" />
+</a>

package/node_modules/yaml/bin.mjs

@@ -0,0 +1,11 @@
+#!/usr/bin/env node
+
+import { UserError, cli, help } from './dist/cli.mjs'
+
+cli(process.stdin, error => {
+  if (error instanceof UserError) {
+    if (error.code === UserError.ARGS) console.error(`${help}\n`)
+    console.error(error.message)
+    process.exitCode = error.code
+  } else if (error) throw error
+})

package/node_modules/yaml/browser/dist/compose/compose-collection.js

@@ -0,0 +1,88 @@
+import { isNode } from '../nodes/identity.js';
+import { Scalar } from '../nodes/Scalar.js';
+import { YAMLMap } from '../nodes/YAMLMap.js';
+import { YAMLSeq } from '../nodes/YAMLSeq.js';
+import { resolveBlockMap } from './resolve-block-map.js';
+import { resolveBlockSeq } from './resolve-block-seq.js';
+import { resolveFlowCollection } from './resolve-flow-collection.js';
+
+function resolveCollection(CN, ctx, token, onError, tagName, tag) {
+    const coll = token.type === 'block-map'
+        ? resolveBlockMap(CN, ctx, token, onError, tag)
+        : token.type === 'block-seq'
+            ? resolveBlockSeq(CN, ctx, token, onError, tag)
+            : resolveFlowCollection(CN, ctx, token, onError, tag);
+    const Coll = coll.constructor;
+    // If we got a tagName matching the class, or the tag name is '!',
+    // then use the tagName from the node class used to create it.
+    if (tagName === '!' || tagName === Coll.tagName) {
+        coll.tag = Coll.tagName;
+        return coll;
+    }
+    if (tagName)
+        coll.tag = tagName;
+    return coll;
+}
+function composeCollection(CN, ctx, token, props, onError) {
+    const tagToken = props.tag;
+    const tagName = !tagToken
+        ? null
+        : ctx.directives.tagName(tagToken.source, msg => onError(tagToken, 'TAG_RESOLVE_FAILED', msg));
+    if (token.type === 'block-seq') {
+        const { anchor, newlineAfterProp: nl } = props;
+        const lastProp = anchor && tagToken
+            ? anchor.offset > tagToken.offset
+                ? anchor
+                : tagToken
+            : (anchor ?? tagToken);
+        if (lastProp && (!nl || nl.offset < lastProp.offset)) {
+            const message = 'Missing newline after block sequence props';
+            onError(lastProp, 'MISSING_CHAR', message);
+        }
+    }
+    const expType = token.type === 'block-map'
+        ? 'map'
+        : token.type === 'block-seq'
+            ? 'seq'
+            : token.start.source === '{'
+                ? 'map'
+                : 'seq';
+    // shortcut: check if it's a generic YAMLMap or YAMLSeq
+    // before jumping into the custom tag logic.
+    if (!tagToken ||
+        !tagName ||
+        tagName === '!' ||
+        (tagName === YAMLMap.tagName && expType === 'map') ||
+        (tagName === YAMLSeq.tagName && expType === 'seq')) {
+        return resolveCollection(CN, ctx, token, onError, tagName);
+    }
+    let tag = ctx.schema.tags.find(t => t.tag === tagName && t.collection === expType);
+    if (!tag) {
+        const kt = ctx.schema.knownTags[tagName];
+        if (kt?.collection === expType) {
+            ctx.schema.tags.push(Object.assign({}, kt, { default: false }));
+            tag = kt;
+        }
+        else {
+            if (kt) {
+                onError(tagToken, 'BAD_COLLECTION_TYPE', `${kt.tag} used for ${expType} collection, but expects ${kt.collection ?? 'scalar'}`, true);
+            }
+            else {
+                onError(tagToken, 'TAG_RESOLVE_FAILED', `Unresolved tag: ${tagName}`, true);
+            }
+            return resolveCollection(CN, ctx, token, onError, tagName);
+        }
+    }
+    const coll = resolveCollection(CN, ctx, token, onError, tagName, tag);
+    const res = tag.resolve?.(coll, msg => onError(tagToken, 'TAG_RESOLVE_FAILED', msg), ctx.options) ?? coll;
+    const node = isNode(res)
+        ? res
+        : new Scalar(res);
+    node.range = coll.range;
+    node.tag = tagName;
+    if (tag?.format)
+        node.format = tag.format;
+    return node;
+}
+
+export { composeCollection };