Project Structure - Krono

Krono organizes its applications and shared logic into distinct packages to promote code reuse and separation of concerns.

Directory Layout

We use a standard Turborepo structure where shared libraries live in packages/ and deployable applications live in apps/.

krono/
├── apps/
│   ├── web/          # The main Next.js demo application
│   ├── docs/         # This documentation site (Mintlify)
│   └── storybook/    # Component development environment
├── packages/
│   ├── core/         # Vanilla TS business logic (WebSocket, Orderbook)
│   ├── hooks/        # React hooks wrapping the core logic
│   ├── kit/          # UI components (shadcn/ui + Tailwind)
│   ├── ui/           # Shared internal UI utilities
│   └── tsconfig/     # Shared TypeScript configurations
├── examples/         # Implementation examples for users
└── package.json      # Root configuration

Technology Stack

Krono is built on a modern, type-safe stack designed for performance and developer experience.

Tool	Category	Purpose
TypeScript	Language	Static type checking for safer code
Turborepo	Build System	High-performance monorepo management
Bun	Runtime	Fast installation, testing, and script execution
Biome	Quality	Lightning-fast linting and formatting
Vitest	Testing	Unit and integration testing framework
Playwright	Testing	Reliable end-to-end testing
shadcn/ui	UI	Accessible, unstyled component primitives