Author

Powerduck

4 min read

Detect breaking API changes in CI with OpenAPI diffs (before your customers do)

Most breaking API changes ship silently: a removed enum value, a field turned nullable, a new required parameter, a tightened status code. OpenAPI diffing in CI classifies changes as breaking or non-breaking, blocks the dangerous ones, and turns API review from memory into a checklist.

Read article
2 min read

The backend was three weeks late. We shipped the frontend anyway.

A concrete sprint diary: one OpenAPI file drove a local mock with latency and error overrides, a four-step checkout scenario with an HTML report, live docs, derived database tables and a hosted MCP endpoint while the real API did not exist yet.

Read article
2 min read

Don't block frontend work on a backend that isn't ready

Fake objects in components demo well and integrate badly. Agree on the coupon validation contract first, then let a spec-driven mock answer real HTTP while the service is still being built.

Read article
2 min read

Your AI codes fast. The integration is still wrong.

Generated screens fail on limit versus pageSize, data.records versus data.items, cents versus dollars. The fix is not a better prompt; it is letting the agent query the real contract and verify against real responses.

Read article
5 min read

Mocking APIs for frontend development: MSW vs Prism vs spec-driven mocks

MSW intercepts requests inside the browser and shines in component tests; Prism serves a spec over HTTP and validates contracts; spec-driven workspaces add journeys and streams. Here is where each belongs and how teams combine them without maintaining three sets of fixtures.

Read article