• 0.4.0 5c7f72682b

    Version: 0.4.0 - Initial Release
    All checks were successful
    CI / ci (pull_request) Successful in 1m45s
    Dist Linux / dist-linux (release) Successful in 3m14s
    Stable

    mburchard released this 2026-03-01 21:46:28 +00:00 | 15 commits to main since this release

    First public release of the Vite Electron Starter template.

    Highlights

    • Vite-powered build with HMR for main process, preload script, and renderer. No third-party Electron plugins, everything is transparent in
      vite.config.ts.
    • Multi-page support via project.config.ts with virtual module resolution and template variable injection.
    • Window management with pack mode (auto-sizing to content), flexible placement, display-awareness for multi-monitor setups, and target screen
      selection (primary, app, active).
    • Dialogue system replacing native Electron dialogues with fully styled, configurable windows. Five visual types, configurable buttons,
      lifecycle hooks, and a convenience API (showConfirm, showError, showInfo, showSuccess, showWarning).
    • Type-safe IPC with four communication patterns: request-response, fire-and-forget, broadcast, and targeted send. Fully sandboxed renderer via
      contextBridge.
    • Production-ready logging powered by bit-log with source map support, coloured console
      output, and daily rotating log files. Backend and frontend events are merged chronologically via a custom PipelineAppender.
    • Security defaults: Context Isolation, Sandbox, strict CSP enabled. Node Integration and Webview disabled.
    • CI/CD pipelines for lint, typecheck, test, and coverage on Forgejo, plus automated distribution builds (Linux AppImage, macOS DMG, Windows
      Squirrel).
    • Clean separation of core functionality and demo code. Delete the demo/ subdirectories for a minimal starter.

    Tech Stack

    Electron 40, Vite 7, TypeScript 5.9, pnpm 10, ESLint 10 + @antfu/eslint-config, Vitest 4, electron-builder

    Note

    This is the first release, primarily to test the automated distribution workflows. Platform-specific installers may be attached as assets if the
    builds succeed.

    Downloads