CtrlK
BlogDocsLog inGet started
Tessl Logo

tessl-labs/typescript-project-structure

TypeScript project structure, strict tsconfig, module resolution, path aliases, shared types, and monorepo patterns

90

1.09x
Quality

84%

Does it follow best practices?

Impact

100%

1.09x

Average score across 5 eval scenarios

SecuritybySnyk

Passed

No known issues

Overview
Quality
Evals
Security
Files

task.mdevals/scenario-2/

Express API — TypeScript Project Setup

Problem/Feature Description

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.

Output Specification

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 project
  • eslint.config.js — ESLint with typescript-eslint
  • src/index.ts — Express app entry point
  • src/routes/tasks.ts — Task CRUD route handlers
  • src/routes/users.ts — User route handlers
  • src/services/taskService.ts — Task business logic
  • src/services/userService.ts — User business logic
  • src/types/index.ts — Shared type definitions (Task, User, API request/response types)
  • src/lib/config.ts — Application configuration

The 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

tile.json