CtrlK
BlogDocsLog inGet started
Tessl Logo

simon/skills

Auto-generated tile from GitHub (10 skills)

92

1.16x
Quality

94%

Does it follow best practices?

Impact

92%

1.16x

Average score across 44 eval scenarios

SecuritybySnyk

Advisory

Suggest reviewing before use

Overview
Quality
Evals
Security
Files

task.mdevals/scenario-19/

Project Bootstrap: Node.js TypeScript Service

Problem/Feature Description

A small backend team is starting a greenfield microservice in TypeScript. The team has historically used ts-node for local development and a separate tsc compile step in CI, but this has been causing headaches: a slow compile step before every test run, subtle differences between the TypeScript version used in the dev compiler and the one in the type-checker, and an extra dist/ folder cluttering the repo.

A senior engineer has proposed switching to a workflow where TypeScript files are run directly without any compilation step, taking advantage of capabilities in modern Node.js releases. The team wants a clean project scaffold to prove this out before committing the whole team to the new approach.

Your job is to create a working project scaffold that demonstrates this approach. The project should include a small HTTP server (src/server.ts) with at least one route that responds to GET requests, and a matching test file (test/server.test.ts) that exercises it. The code itself can be minimal — the priority is the correct project configuration and TypeScript code patterns.

Output Specification

Produce a complete, self-contained project in the current working directory with:

  • package.json — configured appropriately for the runtime and module system
  • tsconfig.json — TypeScript configuration suitable for this development workflow
  • src/server.ts — a minimal HTTP server with at least one GET endpoint
  • src/types.ts — a shared type definition file imported by server.ts using the correct import style for this workflow
  • test/server.test.ts — a test file for the server using Node.js built-in tooling
  • A README.md explaining how to run the server and the tests

The README.md must include the exact commands needed to run the server and to run the tests — these should demonstrate the chosen workflow clearly.

evals

README.md

tile.json