// Produces production Electron builds for Fantasia Archive with electron- builder and Quasar. Use when changing build scripts, packaging, or publish flags, or when the user asks how to ship the desktop app.
Works on Fantasia Archive Electron main process: app lifecycle, window management, platform tweaks, native integrations, and ipcMain registration (register*Ipc + electron-ipc-bridge channel names). Use when editing electron-main.ts, src-electron/mainScripts/, or main-side tests.
Global keyboard shortcuts (faKeybinds): renderer matching, Pinia store, main-process persistence over IPC, and Keybind settings UI. Use when adding or changing app-wide shortcuts, capture validation, or bridge APIs for keybind storage.
Sets up and runs Fantasia Archive locally using Yarn, Node.js 22.22 or newer, and Quasar Electron mode. Use when installing dependencies, choosing dev vs production build commands, or when the user mentions environment setup, CLI, or first run.
Runs and extends Fantasia Archive tests: Vitest unit tests vs Playwright component and E2E tests, including rebuild-before-Playwright rules and file naming. Use when writing tests, debugging CI, or when the user mentions Vitest, Playwright, component tests, or e2e.
Migrates Fantasia Archive features to two-level functions + managers layout: pure scripts/functions/, *_manager.ts wiring (underscore suffix, e.g. dialogFoo_manager.ts), thin Vue SFCs. Use when refactoring features, fixing fa-two-level ESLint violations, or adding new UI.
Designs SQLite usage in Fantasia Archive’s Electron main process: file locations under userData, native better-sqlite3 module constraints, and migrations. Use when editing electron-main database code, schema, or persistence paths.
| name | fantasia-release-build |
| description | Produces production Electron builds for Fantasia Archive with electron- builder and Quasar. Use when changing build scripts, packaging, or publish flags, or when the user asks how to ship the desktop app. |
package.json)yarn quasar:build:electron: quasar build -m electron --publish never — local/production artifact without publishing step from Quasar’s perspective (full log stream).yarn quasar:build:electron:summarized: same build via .utility-scripts/quasarBuildElectronSummarized.mjs — minimal terminal noise; full log in test-results/quasar-build-electron-last.log on failure. Used by yarn testbatch:ensure:*.yarn quasar:dev:electron: Development mode with hot reload.package.json engines.node (same floor as Quasar CLI v2 / CI setup-node 22.22).quasar.config.ts and Quasar docs for Electron targets).yarn testbatch:verify (testing-terminal-isolation.mdc).yarn quasar:build:electron (separate terminal); smoke-test the packaged app on target OS(es).yarn test:components, yarn test:e2e) — see fantasia-testing.yarn testbatch:ensure:nochange instead of piecing commands manually (or run yarn test:storybook:smoke and yarn test:storybook:visual separately after the build steps as needed).package.json version as the source of truth and keep changelog headings aligned to it.types/)interface / type declarations in repository-root types/ (import with app/types/...). Prefer one domain-oriented module per feature area with brief JSDoc on exports (see types/I_appMenusDataList.ts). Do not add colocated <filename>.types.ts under src/, src-electron/, or .storybook-workspace/. Ambient augmentations for third-party modules also live under types/ and are loaded with a side-effect import from the owning boot file or src/stores/index.ts (see types/piniaModuleAugmentation.ts)..js), TypeScript (.ts), Vue (.vue), and JSON (.json, .jsonc, .json5) files, enforce expanded multi-line object literals via ESLint (object-curly-newline + object-property-newline) and keep files auto-fixable with eslint --fix.