Skip to the content.

Development

Everything you need to build, run and release eve-online-tooling from source. For what the app is and how to install a prebuilt binary, see the README.

Built with Tauri 2 (Rust core) + React / TypeScript (Vite). Market and character data come from EVE’s ESI API; blueprint/material data from the SDE.

Getting started

1. Install prerequisites

2. Install dependencies

npm install

3. Run the app

npm run tauri dev      # launches the desktop app with hot reload

The first time you open the Production module it downloads the EVE SDE (a few hundred MB, Fuzzwork’s SQLite build) into your app data dir; that’s a one-off.

No audio / GStreamer element appsink not found on Linux? The WebView plays audio (the Scripts play_sound) through GStreamer. A snap terminal (e.g. Alacritty-as-snap) exports GST_PLUGIN_SYSTEM_PATH / GST_PLUGIN_SCANNER / LD_LIBRARY_PATH pointing at its own sandbox, which lacks those plugins. The app now strips those snap paths at startup so audio works regardless; if you still hit it (an unusual snap layout), launch from a non-snap terminal or run: env -u GST_PLUGIN_SYSTEM_PATH -u GST_PLUGIN_SCANNER -u GST_PLUGIN_PATH_1_0 -u LD_LIBRARY_PATH npm run tauri dev.

4. EVE SSO

Logging a character in works out of the box: the app ships with its own public EVE developer-application Client ID (CLIENT_ID in src-tauri/src/esi/oauth_exchange.rs, native PKCE, no secret) and the loopback callback http://localhost:8765/callback. The requested scopes are the SCOPES list in the same file. Only if you point a fork at your own application at developers.eveonline.com do you need to register your own Client ID, that callback, and enable every scope in SCOPES (SSO rejects the whole login otherwise). Not required for the market/production calculations, which use public data.

Common commands

Command What it does
npm run tauri dev Run the desktop app (hot reload)
npm run tauri build Build distributable bundles
npm run build Type-check + build the frontend
npm run generate:bindings Regenerate the tauri-specta TS bindings (CI fails if the committed files drift)
node scripts/check-tauri-versions.mjs Check Tauri crate/npm major.minor versions match in the lockfiles
npm run test Frontend unit tests (Vitest)
cd src-tauri && cargo test Rust unit tests

Every PR runs two GitHub Actions workflows: CI (.github/workflows/ci.yml) — the merge gate: lint, format, tests, npm run build, the bindings drift check, the Tauri version-alignment check, cargo fmt/clippy/test. npm run tauri build is not part of every PR: a Linux tauri build --bundles appimage,deb job runs only for release PRs (chore/v*) and PRs/pushes that touch Cargo.toml, Cargo.lock, package.json, package-lock.json or tauri.conf.json. Windows/macOS-only code is compiled only by the post-merge cache warm and the Release workflow. And Security (.github/workflows/security.yml) — CodeQL (JS/TS + Rust) and dependency audits (npm audit, cargo audit). Security also runs weekly against main, so newly-disclosed advisories surface without a new PR. Its audit jobs are currently informational (continue-on-error) rather than merge- blocking, since the existing dependency tree has known advisories that need a deliberate, tested bump rather than a silent CI-driven one — flip that off once those are triaged.

SDE-gated tests (fitting golden suite)

The fitting engine’s golden tests (modules::fitting::golden_tests and the other tests that need game data) run against the real Fuzzwork SDE. Point EVE_SDE_PATH at the sde.sqlite file — the one the app downloaded, e.g. ~/.local/share/com.thlange.eve-online-tooling/sde/sde.sqlite (Linux), or any decompressed copy of https://www.fuzzwork.co.uk/dump/latest-sqlite.db.gz:

EVE_SDE_PATH=~/.local/share/com.thlange.eve-online-tooling/sde/sde.sqlite \
  cargo test --manifest-path src-tauri/Cargo.toml --lib modules::fitting

Without the variable those tests print a “skipping” note and pass; with it set to a path that isn’t a file they fail. The shared helper test_support::test_sde() (src-tauri/src/test_support.rs) opens the file and derives the app-data directory the engine expects (<dir>/sde/sde.sqlite; a temp-dir symlink is made when the file lives elsewhere) — use it for any new SDE-gated test rather than reading the variable yourself. The Fitting (real SDE) workflow (.github/workflows/fitting-sde.yml) runs them in CI on PRs touching src-tauri/src/modules/fitting/** or src-tauri/src/sde/**, on pushes to main and weekly (the SDE archive is cached by Fuzzwork’s md5, so it only re-downloads when the dump changes).

See CLAUDE.md for architecture and EVE domain notes, and the other docs for subsystems: plugins, scripts, MCP.

Implementation notes

Releasing

Installers are produced by the Release GitHub Actions workflow (.github/workflows/release.yml). To cut a release:

  1. On a chore/vX.Y.Z branch, bump the version everywhere at once: scripts/bump-version.sh 0.25.0 (edits package.json, src-tauri/Cargo.toml, src-tauri/tauri.conf.json and regenerates both lockfiles). Review the diff and commit chore(release): v0.25.0.
  2. Open a PR and enable auto-merge (gh pr merge --auto --merge --delete-branch); CI gates it. Never push to main directly (see AGENTS.md).
  3. Tag the resulting merge commit on main and push only that tag: git tag v0.25.0 <merge-commit> && git push origin v0.25.0.

The workflow builds Windows, macOS (universal) and Linux installers on every v* tag. It refuses to run from a non-tag ref and fails fast if the tag does not match the versions in package.json, Cargo.toml and tauri.conf.json. It attaches the installers to a draft GitHub Release, which is published (with the changelog and the unsigned-build note, see SIGNING.md) only once every platform leg has succeeded.

Keep @tauri-apps/cli at ≥ 2.12 (bundler ≥ 2.10): older bundlers copy the build host’s /usr/bin/xdg-open into the AppImage whenever tauri-plugin-opener is a dependency. On the ubuntu-22.04 runner that is xdg-utils 1.1.3, AppRun puts it ahead of the system one on PATH, and its open_kde() only handles KDE_SESSION_VERSION 4 and 5 — on KDE Plasma 6 it exits 0 without doing anything, so EVE SSO (and every other external link) silently never opened a browser (#1140).

Status & tracking

Work is tracked as GitHub issues (afk = mergeable without a human, hitl = needs a human).