Stack
The technologies that power each digital experience.
Kotkoroid Patterns is anchored to the Cloudflare Developer Platform. Each technology clears two bars: how well it runs on the edge, and whether it meets the standards held across the codebase.
Language
Section titled “Language”Every project is built exclusively in TypeScript with ES modules throughout. Compiler settings are tuned for absolute peace of mind around static typing, and compiler has the final word — every escape hatch, from any and type assertions to @ts-ignore and non-null assertions, is in production code treated as a defect rather than a tool.
Runtime
Section titled “Runtime”Code runs on Cloudflare Workers in every environment but local, where the same workerd runtime executes it behind a local HTTP proxy. Resources always live on the edge — every environment has its own set, isolated from the rest. Consistency between production and development is treated as a standard, not a hope.
Scripts and tooling run on Bun. Chosen for performance — at the toolchain layer, iteration time compounds across every command.
Dependencies
Section titled “Dependencies”Dependencies come from npm and JSR, with JSR preferred when both carry the same one. JavaScript ships without a standard library, so @std is the default fill — except where Effect already covers the same ground, which takes precedence.
Package Manager
Section titled “Package Manager”Package management runs through Bun. The codebase is organized into workspaces that take the shape of a monorepo — every workspace is a project, and cross-references resolve like any other dependency.
The lockfile is frozen and the linker is isolated — every install is reproducible, and every project sees only the dependencies it declares.
Orchestration
Section titled “Orchestration”Task orchestration runs through Nx, which leverages Bun’s workspaces. Every task executes in dependency order across the project graph — results are cached and reused, so unchanged work never repeats.
Version Control
Section titled “Version Control”Source code is tracked with Git, with GitHub hosting the canonical remote. Pull requests are the only path to the persistent branches — every one passes through review and the pipeline before merging.
Framework
Section titled “Framework”All backend code is built on Effect. Control flow, concurrency, and error handling all run through its primitives — projects compose Effect rather than rolling their own foundations.
Deployment
Section titled “Deployment”Every environment, from local development to production, is provisioned through Alchemy. Cloud resources and runtime logic share the same program — bindings flow between them at the type level, and running it brings every resource to its declared state.