Building with Nwire
This is the 80% path: you want to build a backend, you want Nwire's full stack, and you want to start small and add capability as the domain demands it.
The reading order is a ladder. Start at L1 with one HTTP route. When you need DI, climb to L2. When you need plugins and lifecycle, L3. When you need actors, events, projections, and workflows, L4.
The ladder
| Level | What you add | What you can do | Page |
|---|---|---|---|
| L1 | @nwire/http + @nwire/endpoint | Typed routes, OpenAPI, graceful shutdown | L1 — Minimal HTTP |
| L2 | @nwire/container | Bring-your-own DI (constructor + factory + interface tokens) | L2 — + Container |
| L3 | @nwire/app | Plugin lifecycle (provide / on / boot / shutdown) | L3 — + App |
| L4 | @nwire/forge | Actors, events, projections, workflows, Studio | L4 — + Forge |
You can stop at any level. You can also skip levels — L4 reads everything in L1-L3 for you when you createApp. The ladder exists so you don't have to swallow the whole framework on day one.
Getting started
- What is Nwire? — one page, code-first
- Install + your first endpoint — L1 walkthrough, one route, running locally in two minutes
Common recipes
When you need a specific cross-cutting capability, jump straight to the recipe.