dsh-api-mock

Frontend work kicks off, but the backend APIs are still in sprint planning. You cannot render real data, exercise state transitions, or test error paths — a familiar stall for every frontend developer. dsh-api-mock takes a very direct approach: it reads an OpenAPI 3.x specification (JSON or YAML) and immediately outputs a zero-dependency, single-file Node mock server. It relies only on the built-in http module, has no npm packages, no Docker, and no network calls. One line — node mock-server.mjs — brings every endpoint online with schema-conformant sample responses, so the frontend can start integration work right away.

The plugin registers two tools. mock_generate does the heavy lifting: it parses the spec, locates the first 2xx application/json response schema per operation, emits the complete server file, and returns a list of available endpoints with the run command. mock_sample is lighter and more targeted: given a schema type or an operationId it produces a single example JSON value, handy for quick test fixtures or seed data. All sample values are deterministic — strings get a placeholder, integers get 42, email fields get user@example.com, enums resolve to the first item — while still honouring any example, default, or enum already declared in the spec.

The scenario it targets is straightforward: you have a reasonably complete OpenAPI document (even a shared Swagger export), but the backend timeline lags behind frontend needs; or you are building an independent project and want to wire up interactions before real data exists; or you just need to give a new teammate a clickable, immediate view of the API surface. No microservices to spin up, no Jest fixtures to hand-write — open a terminal, run the generate command, and the browser shows structured JSON.