How gizmo-ds/vcc-auto-translate works
Project type and purpose
• This is a “patcher”/translation tool for a desktop application (VRChat Creator Companion, or VCC).
• It consists of two main codebases:
• A TypeScript “patch-loader” that uses AST techniques to inject translations into VCC’s React code.
• A Rust-based CLI installer that bundles the patch-loader and applies it to the user’s VCC installation.
File structure
• Top level:
• package.json, pnpm-lock.yaml, tsconfig.json – define the Node/TS build environment.
• scripts/ – TS build scripts (build-patch-loader.ts, version.ts, localization_hashs.ts).
• src/ – source of the patch-loader and injector logic.
• crates/installer/ – Rust project that compiles to an executable installer.
• localization/ – JSON files with translation mappings.
• images/, docs/ – assets for README and documentation.
• Makefile – orchestrates the build of both TS and Rust parts.
• Patterns:
• A build pipeline: TS sources + localization data → bundled patch-loader.js → embedded into Rust installer assets.
• Runtime: Rust installer invokes patch-loader.js to modify VCC files on disk.
README for additional insights
• Purpose: automatically translate VCC interface by patching its WebApp/Dist/index.html using AST.
• Build steps: pnpm run build:patch-loader → copy built JS into crates/installer/assets → cargo build --release.
• Usage: user downloads the installer binary and runs it in the VCC installation directory.
Elements
• Blue for build-time artifacts/processes.
• Green for runtime installer activities.
• Gray for the target application.
• Rectangles for code modules.
Summary
• Both build and runtime workflows.
• Separate concerns visually: TS vs. Rust vs. VCC target.