nntrivi2001
c7dbaf2d9f
Two leftovers from the rebrand, done together because they touch the same docs and manifests. **Data directory.** `agent-dashboard` could not simply be renamed in the source: it names a real directory holding the live SQLite database. Startup now moves it once, via `migrateLegacyDataDir()` in `server/lib/claude-home.js` — a same-filesystem rename, so it is instant even at multiple gigabytes and cannot leave two divergent copies. `getDataDir()` stays PURE and resolves to the legacy path until the move happens; the first version of this put the rename inside the getter, which meant `npm run test:server` relocated the developer's real database as a side effect. The call sits behind `require.main === module` and ahead of the router requires, because those pull in db.js, which opens SQLite at module load. A failed rename is silent and the old directory keeps being used: an unfashionable directory name beats a blank database beside an unreachable one. Same treatment for the port-discovery file (`.agent-dashboard.json` → `.agenthub.json`, old one dropped on write). Not renamed on purpose: the Sagi localStorage keys (renaming silently resets everyone's prefs) and the PWA manifest `id` (changing it orphans an installed app). **MCP server.** 4 tool calls in 46 days across 577,132 events, against 4,556 lines of TypeScript, a 2 MB committed build artifact, and a pre-commit guard that had already blocked commits twice. Deleted: `mcp/`, the maintainer skills and `mcp-reviewer` agent, the build check, `plugins/agenthub/.mcp.json`, `docs/MCP.md`, 12 npm scripts, 5 Makefile targets, and every doc section describing it. Kept, because they are unrelated things sharing the name: the Config Explorer's MCP tab and its API, per-lane Playwright MCP, the agenthub-config plugin's MCP audit, and the historical `mcp__plugin_agenthub_*` events that analytics must keep attributing. Verified: server 1432/1432, client 459/459, tsc clean, prettier clean. Both directions of the migration proven — a sandbox-HOME test run leaves the legacy directory untouched, and a real boot moves it with its contents intact.
47 lines
1.8 KiB
JavaScript
47 lines
1.8 KiB
JavaScript
#!/usr/bin/env node
|
|
/**
|
|
* @file postinstall.js
|
|
* @description Root `postinstall` hook: after a bare `npm install` at the repo
|
|
* root, install the React client's dependencies too, so a single root install
|
|
* yields a buildable/runnable tree (the client's fonts and build deps live in
|
|
* `client/package.json`). The step is a safe no-op when the `client/` workspace
|
|
* is absent — production/Docker stages that copy only the root manifest and
|
|
* the published tarball both install without a client checkout, and must not
|
|
* fail here. Skipped entirely under
|
|
* `npm install --ignore-scripts` (run `cd client && npm install` manually then).
|
|
* @author Nguyễn Ngọc Trí Vĩ <vinnt@smartgift.vn>
|
|
*/
|
|
|
|
const { spawnSync } = require("child_process");
|
|
const fs = require("fs");
|
|
const path = require("path");
|
|
|
|
const clientDir = path.join(__dirname, "..", "client");
|
|
const clientManifest = path.join(clientDir, "package.json");
|
|
|
|
// No client checkout in this context (Docker server stages, packed tarball,
|
|
// server-only installs). Nothing to do — succeed quietly so the parent install
|
|
// is not broken.
|
|
if (!fs.existsSync(clientManifest)) {
|
|
console.log("[postinstall] client/ not present — skipping client dependency install.");
|
|
process.exit(0);
|
|
}
|
|
|
|
console.log("[postinstall] installing client dependencies (client/)...");
|
|
|
|
// `shell: true` is required on Windows so npm's `.cmd` shim resolves (Node
|
|
// rejects spawning `.cmd`/`.bat` directly since 18.20 / CVE-2024-27980); the
|
|
// fixed arg list has no shell-significant characters, so this stays safe.
|
|
const result = spawnSync("npm", ["install"], {
|
|
cwd: clientDir,
|
|
stdio: "inherit",
|
|
shell: true,
|
|
});
|
|
|
|
if (result.error) {
|
|
console.error("[postinstall] failed to launch npm for the client install:", result.error.message);
|
|
process.exit(1);
|
|
}
|
|
|
|
process.exit(result.status === null ? 1 : result.status);
|