How graphif/project-graph works
Project type and purpose
• This is a pnpm/turborepo monorepo hosting three main concerns:
– “app”: a cross-platform desktop/web graph‐editing application built with React + TypeScript (Vite) and Tauri (Rust)
– “docs” (and “docs-pg”): a Next.js-based documentation site
File structure
Top-level
• pnpm-workspace.yaml, turbo.json, GitHub workflows → monorepo orchestration & CI/CD
• app/ → main application
– src/ → React UI components, core engine (renderers, services, controllers, plugins)
– src-tauri/ → Rust backend (Tauri configuration, build.rs, capabilities, Android template)
– package.json, tsconfig, vite.config.ts → JS build & dev tooling
• docs/ & docs-pg/ → Next.js docs site (content, localization, MDX)
• packages/ → independently versioned npm packages:
– api (JS wrapper for Tauri commands)
– data-structures (Queue, Stack, Vector, etc.)
– serializer (serialize/deserialize stage data)
– unplugin-original-class-name (build-tool plugin)
README for additional insights
(app/README.md describes Tauri setup, Vite dev, build targets, key features: rendering engines, plugin API, file import/export, AI integrations, Android generation.)