What we build with
This is the stack behind Packgine, which we built and run in production. We list it because “experienced and reliable” is what every development shop says, and a version number is checkable.
Product engineering
React 19 and TypeScript on TanStack Start, server-rendered and deployed to Nitro edge workers, built with Vite. Routing is file-based with per-route document heads, so what a crawler or an AI agent receives is the same HTML a person receives. Unknown routes return real 404 status codes rather than a soft 200.
Data and application layer
Supabase for Postgres, authentication, and server-side data access. Zod for schema validation at the boundary. TanStack Query for client-side data flow. Typed end to end, so a shape change in the database surfaces at compile time rather than in production.
Interface systems
Tailwind CSS 4 with Radix primitives. Design tokens rather than hard-coded values, full light and dark support, and accessible component behaviour inherited from the primitive layer rather than reimplemented.
Quality gates
Vitest and Testing Library for unit and component tests. ESLint and Prettier enforced. Most usefully: the production build runs a metadata check and a full site crawl, and fails the deploy on duplicate title or description tags, on an internally linked page missing from the sitemap, and on an unknown URL returning the wrong status. Regressions stop at the build rather than reaching production quietly.
Machine readability
Sitemap, RSS, and machine-readable content indexes generated from the data layer at request time rather than from build artifacts, so they cannot drift from the site they describe. JSON-LD structured data for organizations, breadcrumbs, defined terms, and FAQ content.