Recipes
End-to-end migrations: third-party reference apps ported to Nwire. Each recipe is the framework's own integration test — the more diverse apps we port, the more confident the surface is.
Recipe pages are being written as migrations land
The forks are cloned at ~/Projects/nwire/forks/. Migrations write into sibling folders (e.g. ~/Projects/nwire/realworld/). Each recipe page will walk through the rewrite, surface what was awkward, and credit the common modules that fell out.
| Source | What it stress-tests | Recipe page |
|---|---|---|
| gothinkster/realworld | Full app: auth + articles + comments + follow + tags | RealWorld API |
| lokalise/node-service-template | Production patterns: shutdown, health, logging, env | Service template |
| hagopj13/node-express-boilerplate | Validation, RBAC, mailer, file upload | Express boilerplate |
| eldimious/nodejs-api-showcase | Classic REST + clean architecture | API showcase |
| nestjs/nest sample/ | Microservices, gateways, GraphQL, TypeORM | NestJS samples |
What a recipe page covers
Each recipe is structured the same way so you can scan:
- What the original does — quick summary of the source app
- Bounded contexts — how the original's controllers map to Nwire modules
- Per-module migration — action by action, what changes
- Common modules extracted — patterns that became
@nwire/module-* - What got better / what got worse — honest reckoning
- Tests — BDD scenarios from the original's spec, in Gherkin