TypeScript

Localz's frontend language (Next.js 15, App Router, Zod validation mirroring the FastAPI/Pydantic backend) — plus the broader Node.js ecosystem.

Why we need this / what value this brings

TypeScript depth pays off directly on the Localz frontend and keeps the type boundary honest against the FastAPI backend.

When to use this

Any Localz frontend feature, a type-safety question at the API boundary, or general TS/Node fluency gap.

How to use or implement this

Start with FrontendFrameworks, APIsAndTypeSafety, and AsyncConcurrencyPatterns (closest to daily Localz work) before BackendFrameworks/Go-adjacent breadth topics.

Subtopics

• LanguageInternals
• StandardLibraryAndRuntime
• AsyncConcurrencyPatterns
• TestingInTypeScript
• FrontendFrameworks
• BackendFrameworks
• BuildToolingAndBundlers
• PackagingAndPublishing
• APIsAndTypeSafety
• PerformanceOptimization

Research questions

• Which parts of the Localz frontend most need a written-down pattern (server vs client component boundaries, form validation, data fetching)?

Related

• Languages
• FrontendWebMobile (general theory backing FrontendFrameworks/ and PerformanceOptimization/)

---

Empty folder — drop notes, links, and findings here as you research.