Why donate
API Explorer
Upgrade Guide
Creating a New Project
The /quasar.config File
Convert q/app-webpack Project
Browser Compatibility
TypeScript Support
Directory Structure
Commands List
CSS Preprocessors
Page Routing with VueRouter
Lazy Loading - Code Splitting
Handling Assets
Boot Files
Prefetch Feature
API Proxying
Handling Vite
Handling import.meta.env
State Management with Pinia
Lint and Format Code
Testing & Auditing
Developing Mobile Apps
Ajax Requests
Opening Dev Server To Public
Quasar CLI with Vite - @quasar/app-vite v3
Installing Electron-specific dependencies

Use /src-electron/package.json for dependencies that belong to the Electron main process or its packaging workflow. Keeping them in this workspace prevents Electron-only packages from becoming renderer dependencies.

/src-electron/package.json

{
  "name": "quasar-electron-app",
  "version": "1.0.0",
  "description": "Quasar Electron Folder",
  "private": true,
  "type": "module",
  "devDependencies": {
    "electron": "^<installed-version>"
  }
}

Quasar installs the selected packaging tool (@electron/packager or electron-builder) here on the first production build that needs it.

From /src-electron, install packages used at runtime by the main process under dependencies. Install Electron, packaging tools, type packages, and other build-time tools under devDependencies:


# Runtime dependency installed into the packaged app:
pnpm add <deps>

# Build-time dependency:
pnpm add -D <dev-deps>

Renderer dependencies imported by code under /src belong in the root package.json and are bundled by Vite.