PRUNplanner Frontend

The frontend application of PRUNplanner.org, the comprehensive empire and base planning tool.

🚀 Features

• Comprehensive Base Simulation: Design and simulate planetary bases without spending in-game resources, mirroring buildings, production lines, and COGC programs.
• Empire-Wide Management: Coordinate multiple bases and complex supply chains with an integrated overview of material flows and consumption.
• Game Data Integration: Seamlessly pulls up-to-date market, planet, and recipe data via the FIO community API.
• Market Exploration: Dynamic information & charting to visualize historical price trends, supply/demand, and traded volumes.
• Advanced Optimization Tools like ROI & Profit Calculator: Detailed calculations for production costs and profit per area.
• Efficient Material I/O: Visual and data-based analysis of production vs. consumption to identify bottlenecks and resource gaps.

Localization & Community Translations

Driven by the incredible efforts of the PRUNplanner community, our planning tools and features are accessible globally. The platform natively supports multiple languages, with more on the horizon:

🇺🇸 English (Native) | 🇩🇪 Deutsch | 🇷🇺 Русский | 🇨🇳 简体中文

Want to see PRUNplanner in your language or help refine existing strings?

👉 Join our translation project on Crowdin

A huge thank you to the following community members who volunteered their time to translate and maintain PRUNplanner translations:

Language	Core Contributors
🇩🇪 Deutsch	Eisberi
🇷🇺 Русский	hameronlive, Razenpok
🇨🇳 简体中文	YuLun-bili, PHANTOMSPACE, MioandMeow

Development

Stack

• Vue3
• Vite
• Typescript
• Pinia for global state
• Tailwind CSS v4 for styling
• Axios for backend calls
• Zod for data validation
• Vitest as testing framework

Deployment

The app runs in production from the Docker image (see below). Every pull request gets its own preview deployment on Cloudflare Pages.

Getting started

With Node 26 (.nvmrc) and pnpm 10, install dependencies with pnpm install and run the vite development server:

pnpm run dev

Testing and Coverage

PRUNplanners frontend historically lacked proper testing of its non-visual features and data validation. Backend calls can be mocked easily with axios-mock-adapter.

# Run tests
pnpm run test

# Or use vitest-ui
pnpm run test:ui

# Component tests (CI runs them on pull requests)
pnpm run test:components

Environment Variables

Key	Type	Default Value
VITE_API_BASE_URL	string	"https://api.prunplanner.org"
VITE_SHARE_BASE_URL	string	"https://prunplanner.org/shared"
VITE_GAME_DATA_STALE_MINUTES_BUILDINGS	int	1440
VITE_GAME_DATA_STALE_MINUTES_RECIPES	int	1440
VITE_GAME_DATA_STALE_MINUTES_MATERIALS	int	1440
VITE_GAME_DATA_STALE_MINUTES_EXCHANGES	int	30
VITE_GAME_DATA_STALE_MINUTES_PLANETS	int	180
VITE_GAME_DATA_MAX_AGE_MINUTES_BUILDINGS	int	10080
VITE_GAME_DATA_MAX_AGE_MINUTES_RECIPES	int	10080
VITE_GAME_DATA_MAX_AGE_MINUTES_MATERIALS	int	10080
VITE_GAME_DATA_MAX_AGE_MINUTES_EXCHANGES	int	30
VITE_GAME_DATA_WRITE_DELAY_MS	int	5000
VITE_INDEXEDDB_DBNAME	string	"prunplanner"
VITE_KIT_PAGE	string	unset ("true" adds the /dev/kit page)

The app version comes from version in package.json, not from an env var.

Build & Run Frontend

PRUNplanner offers a pre-built ARM64 Docker image for the frontend hosted on GitHub Container Registry: prunplanner-frontend. The image comes with default environment settings and rebuilds on published repository releases.

You can also build and run yourself with Docker:

# Build local
docker build -t prunplanner-frontend:latest .

# Run local build
docker run -p 80:80 prunplanner-frontend:latest --brotli --port 80

# or, run pre-built image (ARM64 only)
docker run -p 80:80 ghcr.io/prunplanner/prunplanner-frontend:latest --brotli --port 80

Or use it with Docker Compose, as in the repo's docker-compose.yaml:

services:
    frontend:
        image: ghcr.io/prunplanner/prunplanner-frontend:latest
        container_name: prunplanner-frontend
        entrypoint: ["sh", "-c"]
        command: >
            "echo \"window.__APP_CONFIG__ = { POSTHOG_KEY: '${POSTHOG_KEY}' }\" > /code/env.js &&
            /bin/go-http-server --port 80 --brotli"
        ports:
            - "80:80"
        restart: unless-stopped

index.html loads a runtime /env.js (window.__APP_CONFIG__) for the PostHog key; the compose file writes it from POSTHOG_KEY before starting the server. The plain docker run commands above don't write it, so the app runs with analytics off.