Skip to content

Local Toolchain Snapshot

Disponible en francais

Snapshot captured on 2026-03-30 for the machine currently maintaining this repository. Treat it as a working baseline, not a universal requirement.

ToolVersionRole
nodev22.22.2Default JavaScript runtime
npm10.9.7Bundled package manager and fallback CLI
pnpm10.33.0Recommended package manager for repo commands
bun1.3.11Secondary runtime and utility CLI
deno2.7.9Secondary runtime for specific scripts or tooling
ToolVersionRole
code1.113.0VS Code fallback and extension ecosystem
cursor2.6.21Primary editor-side AI coding surface
claude2.1.85Terminal AI for repo-wide changes and workflows
ToolVersionRole
git2.50.1Source control
gh2.89.0GitHub CLI
docker29.3.1Containers, MCP gateway, and local service tooling
wrangler4.77.0Cloudflare development and deployment
brew5.1.1System package manager
ToolVersionRole
python33.12.13Utility scripts and Python ecosystem support
uv0.11.2Fast Python package and environment management
rustc1.94.1Native tooling support
cargo1.94.1Rust package manager and build tool
ToolStatusNotes
cloudflarednot installedUseful for tunnels and some preview workflows
pipxnot installedHelpful if Python CLI usage grows
gonot installedOnly needed when a specific tool depends on it
gemininot installedOptional second AI CLI
aidernot installedOptional terminal AI workflow
opencodenot installedOptional alternative AI coding CLI
  • modern TypeScript application development
  • Cloudflare-first deployment workflows
  • AI-assisted editing with Cursor and Claude Code
  • using Python or Rust tooling when a supporting script needs it
  • node + pnpm for repo-level commands and examples
  • wrangler + docker for platform and local infrastructure workflows
  • cursor or code in the editor, with claude for terminal-oriented work

bun and deno are useful to have installed, but the repo should not require them by default unless the stack direction changes.

  1. Install cloudflared if preview tunnels, callbacks, or browser/device sharing become common.
  2. Install pipx if Python-based CLIs become a regular part of the workflow.
  3. Add a second AI CLI only if you want model diversity for comparison, not just more tools.
  4. Add go only when a concrete dependency or internal tool actually needs it.