How tsenoner/protspace_d3 works
Project Type and Purpose
• ProtSpace is a monorepo (managed by Turborepo) that delivers a framework-agnostic set of web components for interactive protein‐space visualization, plus a React bridge and a Next.js demo app.
High-Level File Structure Analysis
• Root (monorepo)
– turbo.json, pnpm-workspace.yaml: orchestrate builds and scripts
– .changeset/: version and changelog management
– docs/: design specifications, migration guides, feature lists
– examples/: standalone Vite demos
• packages/
– react-bridge (@protspace/react): React wrappers and hooks around core components
• app/
– Next.js 14 demonstration app (uses React bridge & core)
• examples/
– scatterplot-vite: minimal Vite + core/components demo
• CI/CD and Storybook configurations
Key Components and Their Relationships
• Component Integration:
• React-bridge wraps core APIs and exposes hooks (useProtspaceData, onPointSelect).
• Next.js demo (app/) imports React-bridge (and through it core + utils).
• Examples import core & utils directly for framework-agnostic usage.
• Build & Dev Tools: pnpm + Turborepo handle parallel builds, caching, and filtering; Storybook serves core components in isolation.
Architectural Patterns & Principles
• Monorepo with clearly separated packages (core, utils, react-bridge)
• Publishable, versioned modules via Changesets
• Dependency inversion: core components depend only on utils; react-bridge depends on core; app depends on react-bridge
• Reusable, framework-agnostic design (Web Components via Lit)
• Demo and examples decoupled from core logic