packages/
Shared code lives here once it has a real owner and real content: an empty
package would only add build configuration to maintain (IMPLEMENTATION_PLAN.md
Step 2, FRONTEND_ARCHITECTURE.md §6). First package: supabase/ (Step 3).
Planned packages and the step that creates each one:
| Package | Content | Created at |
|---|---|---|
@faunosteo/domain |
Zod schemas: report document, anatomical sheet document, species, entitlement capabilities | Step 4 (sheet model) |
@faunosteo/anatomy |
SVG convention parser, legacy importer, renderer helpers, spine logic | Step 4 |
@faunosteo/pdf |
export / import / attachment, render helpers | Step 6 (PDF v3) |
@faunosteo/i18n |
FR/EN dictionaries (no React) + useT |
first second consumer (public-web or worker) |
@faunosteo/supabase |
browser client factory, generated database types, PGlite harness running the pgTAP suite | created, Step 3 |
@faunosteo/config |
runtime config resolution shared by app, public-web, worker | with public-web |
@faunosteo/ui |
UI primitives and design tokens | only when public-web reuses them |
Convention: a package has its own package.json (name, exports, types),
tsconfig.json extending the root one, and tests beside its sources.