A comprehensive Escape from Tarkov progress tracker built with Nuxt 4, featuring team collaboration, dual game mode support (PvP/PvE), and real-time synchronization via Supabase.

• Dual Game Mode Support: Track progress separately for PvP and PvE modes
• Team Collaboration: Share progress with teammates in real-time
• Task Tracking: Monitor quest completions and objectives
• Hideout Progress: Track module upgrades and parts
• Player Level Progress: Monitor leveling across different factions
• Real-time Sync: Automatic synchronization via Supabase
• Multi-language Support: Available in English, German, Spanish, French, Russian, and Ukrainian

• Framework: Nuxt 4 (SPA mode)
• UI: Nuxt UI component library
• Styling: Tailwind CSS v4
• State Management: Pinia with three-store architecture
• Backend: Supabase (authentication, database, real-time)
• API: Nuxt server-side proxy to tarkov.dev GraphQL API
• Deployment: Cloudflare Pages

Install dependencies:

npm install

Create a .env file with the following variables:

VITE_SUPABASE_URL=your_supabase_project_url
VITE_SUPABASE_ANON_KEY=your_supabase_anonymous_key

The workers/api-gateway Worker uses a Durable Object binding for rate limiting:

• API_GATEWAY_LIMITER (Durable Object)

Start the development server:

npm run dev

The application will be available at http://localhost:3000.

# Lint code
npx eslint .

# Run tests
npx vitest

Build for production:

npm run build

Preview production build locally:

npm run preview

• app/ - Main application source directory
• app/features/ - Feature-specific components organized by domain
• app/components/ - Global/shared UI components
• app/stores/ - Pinia stores for state management
• app/composables/ - Reusable composition functions
• app/pages/ - File-based routing
• app/server/api/ - Nuxt server routes for API proxying
• docs/ - Project documentation and migration guides

For detailed development guidelines, architecture references, and migration progress, see the files in the docs/ directory.

This repository includes both contribution workflow guidance and technical documentation.

How to Contribute (Issues, Branches, PR Process): Open or pick an issue, get assigned, create a focused branch, Use the PR template, and link the issue.

Label System: Issue Types define the kind of work being done, while labels communicate scope, priority, ownership, and status throughout the lifecycle of the issue.

GitHub Project Board: Issues progress through the board from backlog to completion, with transitions driven by issue and pull request activity.

This project remains licensed under the GNU General Public License v3.0. See LICENSE.md for the full license text.