Files
AgentHub/server/lib/yaml.js
T
nntrivi2001 8546748759 chore: maintenance — dependency majors, rename step 4, member Claude config, OpenAPI coverage
Dependencies
- Security: body-parser and multer DoS advisories fixed (npm audit: 0).
- Server: Express 5 (query parser kept "extended", req.body defaults to {},
  SPA catch-all /{*splat}, send-file helper restores Express 4's dot-folder
  rule for sendFile/download, alerts ack route without inline regex),
  better-sqlite3 13, js-yaml 5 (server/lib/yaml.js keeps js-yaml 4's default
  schema), uuid dropped for crypto.randomUUID, node-pty beta.18, multer 2.5.
- Client: React 19, xterm 6 (WebGL renderer replaces the removed canvas one,
  DOM fallback on context loss; Alt+arrow word moves re-mapped), lucide-react 1,
  TypeScript 7, i18next/react-i18next/codemirror minors.

Workspace rename step 4
- `agenthub lanes` and `--lane` exit 1 with "renamed: use …"; client api.ts,
  the CLI and the MCP server call /api/workspaces; /api/lanes stays mounted.

Server mode (S3): members manage their own Claude Code config
- server/lib/cc-target.js resolves whose config a /cc-config request touches
  and gates the router by allowlist; /profiles* and /plugins/update-all stay
  admin-only. Member writes go through write-as, CLI calls through sudo as the
  member (never -y), reads through openSafe; cc_config_changed reaches only
  its owner. Not verified live on an S3 install yet.

Other
- Chat: an HTML file is an artifact only when written whole and not a project
  page (index.html, or under src/, public/, templates/, …).
- OpenAPI covers every /api route; openapi-coverage.test.js guards it.
- read-pool test keeps its event loop alive (its worker is unref'd).
- Docs: plan statuses, checklists, CLI.md, LANES.md, SERVER-MODE.md, API.md.
2026-10-26 14:22:41 +07:00

36 lines
1.1 KiB
JavaScript

/**
* @file yaml.js
* @description js-yaml 5 with js-yaml 4's loading rules, for the YAML files
* AgentHub reads from a user (a repo's docker-compose file, omp's
* `models.yml`/`config.yml`). js-yaml 5's `load` uses the bare YAML 1.2 core
* schema — no `<<` merge keys, no timestamps, `!!binary`/`!!set` refused — and
* throws on an empty document; 4's default schema was core plus exactly those
* tags, and an empty document loaded as `undefined`. A member's file that
* loaded before must load the same now (and `mergedModels` rewrites it).
* @author Nguyễn Ngọc Trí Vĩ <vinnt@smartgift.vn>
*/
const yaml = require("js-yaml");
/** js-yaml 4's DEFAULT_SCHEMA. */
const V4_SCHEMA = yaml.CORE_SCHEMA.withTags([
yaml.mergeTag,
yaml.timestampTag,
yaml.binaryTag,
yaml.omapTag,
yaml.pairsTag,
yaml.setTag,
]);
/** `yaml.load` as js-yaml 4 did it: undefined for a document-less text. */
function load(text) {
try {
return yaml.load(text, { schema: V4_SCHEMA });
} catch (err) {
if (err && /input is empty/.test(err.reason || "")) return undefined;
throw err;
}
}
module.exports = { load, dump: yaml.dump, V4_SCHEMA };