Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/xScherpschutter/Deeztracker/llms.txt

Use this file to discover all available pages before exploring further.

A production build compiles the Rust backend with optimizations, bundles the Vite frontend output, and packages everything into a native installer for the current platform. The resulting binaries are self-contained — users do not need Node.js, Rust, or any development tools installed.

​
Build steps

1

Verify prerequisites

Make sure your development environment is fully configured before building. You need Node.js, pnpm, and the Rust toolchain installed, along with the platform system libraries that Tauri requires.If you have not done this yet, follow the development setup guide first.
2

Install dependencies

pnpm install
Ensure your JavaScript dependencies are up to date before building.
3

Run the production build

pnpm tauri build
This command runs two stages in sequence:
  1. pnpm build — runs vue-tsc --noEmit to type-check the TypeScript source, then Vite bundles the frontend into dist/
  2. Tauri build — compiles the Rust backend in release mode and packages the frontend and binary into platform-native installers
The first production build downloads and compiles all Rust dependencies from scratch. Expect this to take 10–20 minutes on a typical machine. Subsequent builds reuse the Cargo cache in src-tauri/target/ and finish much faster.

​
Build output

Installers are written to src-tauri/target/release/bundle/. The exact subdirectories and file formats depend on the platform you build on:
FormatLocation
MSI installerbundle/msi/Deeztracker_0.1.8_x64_en-US.msi
NSIS installer (.exe)bundle/nsis/Deeztracker_0.1.8_x64-setup.exe
The MSI is suitable for managed deployments. The NSIS .exe is the standard Windows installer for direct distribution.
The app version (0.1.8) comes from the version field in src-tauri/tauri.conf.json. Update that field before building a new release.

​
Bundle configuration

The bundle settings in src-tauri/tauri.conf.json control what installers are produced: 
"bundle": {
  "active": true,
  "targets": "all",
  "icon": [
    "icons/32x32.png",
    "icons/128x128.png",
    "icons/128x128@2x.png",
    "icons/icon.icns",
    "icons/icon.ico"
  ]
}
"targets": "all" instructs Tauri to produce every supported installer format for the current platform. To build only a specific format, replace "all" with a format name such as "msi", "nsis", "deb", or "appimage".
Tauri does not support cross-compilation between Windows and Linux. To produce a Windows installer you must run the build on a Windows machine (or a Windows CI runner), and likewise for Linux. If you need both platforms, use separate CI jobs for each target.

​
TypeScript type checking

The build script in package.json runs vue-tsc --noEmit before Vite bundles the frontend: 
"build": "vue-tsc --noEmit && vite build"
If the type check finds errors, the build stops before any files are written. Fix all TypeScript errors before running pnpm tauri build.

Build docs developers (and LLMs) love

Get started for freeTalk to us