pastilhas
21bedf1418
replaces the per-plugin package.json from earlier tonight. the owner's call, and the reason is one i had not weighed: sharp is ~50 MB of platform binaries and the obvious dependency for anything touching images, so a second and third plugin wanting it would have meant a second and third copy with no version they could converge on. so every plugin's `npmDependencies` merge into ONE generated plugins/package.json, installed into plugins/node_modules/. bun resolves node_modules up the tree, so that directory serves every plugin and none of the platform's own code. ranges intersect rather than alternate. two plugins asking for ^0.33.5 and ^0.33.9 produce "^0.33.5 ^0.33.9", which npm and bun read as AND — the resolved version must satisfy both. `||` would have meant "either", which is the silent version of this failure: one plugin quietly getting a version the other cannot import. incompatible requirements now fail the install with bun's own message, and both askers are named in the steps either way. generated from the plugins ON DISK, like generatePluginSchemas, and never edited — so a package cannot appear there without a plugin having declared it. what this gives up, knowingly: a committed lockfile. ranges are the whole point and a range resolves per machine, so plugin packages are resolved at install time like osDependencies are, and unlike the platform's own. CLAUDE.md is emphatic about frozen lockfiles and 2026-08-04, so it is named in the manifest type rather than left to be discovered. the generated plugins/package.json and lockfile are gitignored — /plugins/*/ only ignores directories, so files at that level needed naming explicitly.
122 lines
4.4 KiB
Plaintext
122 lines
4.4 KiB
Plaintext
# dependencies (bun install)
|
|
node_modules
|
|
|
|
# output
|
|
out
|
|
src/videos/**/out
|
|
dist
|
|
dist_*
|
|
.dist
|
|
runtime-scripts
|
|
*.tgz
|
|
|
|
# code coverage
|
|
coverage
|
|
*.lcov
|
|
|
|
# logs
|
|
logs
|
|
_.log
|
|
report.[0-9]_.[0-9]_.[0-9]_.[0-9]_.json
|
|
|
|
# dotenv environment variable files
|
|
.env
|
|
.env.development.local
|
|
.env.test.local
|
|
.env.production.local
|
|
.env.local
|
|
|
|
# caches
|
|
.eslintcache
|
|
.cache
|
|
*.tsbuildinfo
|
|
|
|
# IntelliJ based IDEs
|
|
.idea
|
|
|
|
# Finder (MacOS) folder config
|
|
.DS_Store
|
|
|
|
src/config.ts
|
|
|
|
# Playwright
|
|
playwright/
|
|
.wwebjs_cache/
|
|
|
|
# generated from index.html by scripts/gen-index.ts
|
|
src/apps/officer-web/index.gen.html
|
|
|
|
# scratch scripts — never commit these
|
|
*.tmp.ts
|
|
|
|
# Sidecar assets published at install time — copies of files that live in each sidecar's own tree.
|
|
public/plugins/
|
|
|
|
# Written by machine-setup.sh to record completed steps; per-machine, never shared.
|
|
.setup-progress
|
|
.setup-answers
|
|
|
|
# Written by officer-setup.sh; per-machine.
|
|
scripts/setup/officer-setup/.setup-progress
|
|
|
|
# Generated by officer-setup, describing THIS install's processes. Never committed:
|
|
# the repository has no ecosystem file at all any more, and the next machine
|
|
# generates its own. See scripts/setup/officer-setup/lib/services.sh.
|
|
ecosystem.config.cjs
|
|
|
|
# The built SPA and the generated plugin module — both describe THIS install's plugin set and are
|
|
# rewritten on every install. See servers/plugins/generate.ts.
|
|
build/
|
|
build.next/
|
|
src/apps/officer-web/Plugins.gen.tsx
|
|
src/databases/officer_db/src/plugin-schemas.gen.ts
|
|
|
|
# drizzle-kit's generated migrations. Nothing applies them — there is no __drizzle_migrations table and
|
|
# `drizzle-kit migrate` has never been run here; `bun db:push` diffs the schema code against the live
|
|
# database and alters it directly. The schema code is the source of truth (src/databases/CLAUDE.md).
|
|
#
|
|
# Ignored rather than merely unused, because `bun db:gen` reads src/schema.ts — whose last line imports
|
|
# plugin-schemas.gen.ts, itself generated from the plugin DIRECTORIES on this machine. So a generated
|
|
# migration describes whichever plugins happen to be checked out here, and committing one would launder
|
|
# per-machine state into the repository: run it with music installed and history gains music_*; run it on
|
|
# a fresh clone and the next commit deletes them again.
|
|
#
|
|
# The old 0000_new_princess_powerful.sql is deleted from the WORKING TREE but left in history. It had 36
|
|
# tables and described a schema from before capabilities, api_keys, the app store and the plugin system
|
|
# existed, including three (task_logs, terminal_containers, queue_jobs) that no longer exist at all.
|
|
#
|
|
# Purging it from history was tried on 2026-08-15 and deliberately undone. This codebase cites 76 commit
|
|
# SHAs in comments and docs as evidence — `totality.ts` points at 2873948 for the websocket incident,
|
|
# `registry.ts` at 044aacf4, CLAUDE.md at f35c145 — and a filter-repo run rewrites every one of them.
|
|
# Three stale files nobody reads in old commits are not worth 76 dangling citations in a codebase whose
|
|
# documentation works by pointing at the commit that proves the claim.
|
|
#
|
|
# Generate one locally whenever a diff is useful to read. It stays local.
|
|
src/databases/officer_db/migrations/
|
|
|
|
# ── plugins/ holds documentation, not plugins ──
|
|
#
|
|
# Every plugin is its own repository (gitea.officer.dev/plugins/*) and arrives here by `git clone` when
|
|
# somebody installs it. A cloned plugin carries its own .git, so leaving it tracked means `git add -A`
|
|
# commits a gitlink — a pointer to a commit this repo does not contain. That happened on 2026-08-15.
|
|
#
|
|
# The trailing slash matters: this ignores DIRECTORIES only, so files at the top of plugins/ —
|
|
# EXTRACTING-A-PLUGIN.md and anything beside it — stay tracked. The documentation about plugins belongs
|
|
# to the platform; the plugins do not.
|
|
/plugins/*/
|
|
|
|
# Generated by src/servers/plugins/npm-deps.ts from every plugin's `npmDependencies`, and installed into
|
|
# plugins/node_modules/. It describes whichever plugins are on THIS machine, so committing one would
|
|
# claim a dependency set nobody chose. The rule above only ignores directories, so these need naming.
|
|
/plugins/package.json
|
|
/plugins/bun.lock
|
|
/plugins/bun.lockb
|
|
|
|
# Visual baselines for the theme extraction — large, machine-specific, regenerate with scripts/theme-snapshot.ts
|
|
.snapshots/
|
|
|
|
# Installed themes, same rule as plugins: a theme is somebody's own work dropped into this directory, not
|
|
# this repository's content. Only the instructions are tracked.
|
|
themes/*
|
|
!themes/*.md
|