Repository navigation
Expand file tree
/
Copy pathpackage.json
More file actions
36 lines (36 loc) · 3.7 KB
/
Copy pathpackage.json
File metadata and controls
36 lines (36 loc) · 3.7 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
{
"name": "inkie-deck-workspace",
"version": "0.0.0",
"private": true,
"description": "Workspace root for Inkie Deck, a web control plane for a fleet of AI agents, and the bundled agent protocol package it is built on",
"license": "Apache-2.0",
"type": "module",
"_comment:engines": "The lowest version that satisfies every engines.node in the installed tree AND sits on an LTS line still receiving security patches. The strictest real constraint is jsdom's ^20.19.0 || ^22.13.0 || >=24.0.0; nothing in the tree needs more than 22.13.0. The old >=22.18.0 had no justification in the history, and written that way it also admitted Node 23, which was never an LTS line and is already end of life. Enforced by engine-strict in .npmrc: without that, this field is advisory and a Node 20 machine installs, typechecks, tests and gates clean.",
"engines": {
"node": "^22.13.0 || >=24.0.0"
},
"packageManager": "pnpm@10.34.5",
"scripts": {
"_comment:run": "A bare-machine run stopped dead here. A reader finishes the README, has every check green, and has no next line to type: the runnable scripts live in packages/deck, and `pnpm dev` at the root answered `Command \"dev\" not found`. Knowing that a pnpm workspace means `cd` into a subdirectory is developer knowledge, and this project's readers are not all developers. These three forward the naive guesses to where they actually live.",
"dev": "pnpm -C packages/deck dev",
"build": "pnpm -C packages/deck build",
"start": "pnpm -C packages/deck start",
"typecheck": "pnpm -r run typecheck",
"typecheck:tsc": "pnpm -r run typecheck:tsc",
"_comment:test": "One workspace at a time, deliberately. pnpm -r defaults to running package scripts in parallel, and the base suite drives bin/create-agent.sh as real subprocesses. Run alongside deck's suite, that load alone pushed a dozen of deck's 5-second per-test timeouts over the line: 64 failures, none of them a real defect, on a tree that is green when the two run in sequence. A suite that fails for load reasons is no more use than one that passes for environmental ones.",
"test": "pnpm -r --workspace-concurrency=1 run test",
"check:boundaries": "depcruise packages",
"_comment:check:leaks": "Three scopes, because a clone hands over more than the working tree. check:leaks answers 'is the checkout clean'. :history answers 'is every reachable object clean', which is the only one that means anything for a repository that has history: a string deleted by a later commit is still served by git show from every tree that carried it. :messages answers the same question for what git log prints, which is the half a reader reaches for first. A green check:leaks over a red check:leaks:history is the exact shape of a repository that looks scrubbed and is not.",
"check:leaks": "node scripts/leak-gate.mjs",
"check:leaks:history": "node scripts/leak-gate.mjs --history",
"check:leaks:messages": "node scripts/leak-gate.mjs --messages",
"check:licence": "node scripts/licence-gate.mjs",
"_comment:check:lib-version": "PANE_IDLE_LIB_VERSION is a safety assertion, not a label: two callers refuse to run against a library older than the version they pin, precisely because an absent function reads as an empty answer rather than as an error. That only holds while one number means one function surface, and nothing else in the build has an opinion about it. The collision this catches was found by hand on a real tree, where a dormant branch had claimed the same version for a different surface.",
"check:lib-version": "node scripts/lib-version-gate.mjs"
},
"devDependencies": {
"@typescript/native-preview": "7.0.0-dev.20260707.2",
"dependency-cruiser": "^16.10.0",
"typescript": "^5.8.0"
}
}