TypeScript project structure, strict tsconfig, module resolution, path aliases, shared types, and monorepo patterns
90
84%
Does it follow best practices?
Impact
100%
1.09xAverage score across 5 eval scenarios
Passed
No known issues
A startup is building a REST API for a task management application using Express and TypeScript. They need the project scaffolded from scratch with proper TypeScript configuration, project structure, and build tooling. The API will have endpoints for managing tasks (CRUD) and users (registration, login).
The team wants strict type safety, clean imports, and a project layout that will scale as the codebase grows. They plan to add tests later and want the structure to support that.
Produce a project structure with the following files:
package.json — with dependencies and scripts (build, dev, start, typecheck, lint, test)tsconfig.json — strict TypeScript configuration with path aliases.gitignore — proper ignores for a TypeScript/Node projecteslint.config.js — ESLint with typescript-eslintsrc/index.ts — Express app entry pointsrc/routes/tasks.ts — Task CRUD route handlerssrc/routes/users.ts — User route handlerssrc/services/taskService.ts — Task business logicsrc/services/userService.ts — User business logicsrc/types/index.ts — Shared type definitions (Task, User, API request/response types)src/lib/config.ts — Application configurationThe application does not need to connect to a real database — use in-memory stores. Focus on project structure, tsconfig setup, and TypeScript patterns rather than complete implementation.
evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
skills
typescript-project-structure
verifiers