package.json

{
  "name": "spyde-workspace",
  "private": true,
  "description": "SpyDE workspace — the app at electron/ + spyde/. The shared shell is the de-shell package (Python + its TypeScript, linked in at electron/shell by electron/scripts/shell-link.mjs); Ground Crew and Autopilot live in their own repos on the same package.",
  "workspaces": [
    "electron"
  ],
  "//": "electron is declared HERE, at the workspace root, so every root-hoisted tool that resolves 'electron' from its own location (electron-vite's version sniff, playwright-core's bare require('electron/index.js')) finds the SAME version the app declares in electron/package.json. Without this, npm's auto-installed peer once put electron 43 at the root and every e2e silently ran the wrong Electron. EXACT, not a range, and it must match electron/package.json: making this a workspace hoisted electron out of electron/node_modules, and electron-builder resolves the installed version from the project dir — it cannot, so it falls back to parsing this spec and REFUSES a range. That is a release-only failure (nothing else runs electron-builder), so it does not show up until the tag build.",
  "devDependencies": {
    "electron": "44.0.0"
  },
  "scripts": {
    "dev": "npm --workspace spyde-electron run dev",
    "build": "npm --workspace spyde-electron run build",
    "preview": "npm --workspace spyde-electron run preview",
    "test": "npm --workspace spyde-electron test",
    "typecheck": "npm --workspace spyde-electron run typecheck",
    "shell:link": "node electron/scripts/shell-link.mjs",
    "postinstall": "node electron/scripts/shell-link.mjs --soft",
    "_comment:test:unit": "The shell's unit tests, run against the linked tree so a shell update is exercised from here too. A missing link makes this fail loudly rather than run nothing — see shell:link.",
    "test:unit": "node --test \"electron/shell/**/*.test.ts\" \"electron/shell/**/*.test.cjs\""
  }
}