Skip to content

Standalone packages ​

Each of the foundational Nwire packages works on its own, with no other Nwire package required. Drop one into your Express / Fastify / Koa / Nest app and use it without buying into the rest of the framework.

The Nwire stack itself is built by composing them — @nwire/forge uses @nwire/app, which uses @nwire/container and @nwire/hooks. If you wire them yourself, you get the same primitives that power the full framework.

Packages ​

PackageWhat it does on its ownPage
@nwire/endpointGraceful shutdown + health probes for any HTTP frameworkRead
@nwire/handlerThe operation primitive — same operation runs on HTTP, queue, or MCPRead
@nwire/hooksUniversal dispatch primitive — tense-driven, typed, ~30 LOC behind itRead
@nwire/containerBring-your-own DI — typed tokens, scopes, no decorators, no reflect-metadataRead

When to use this path ​

  • You have an existing app and you want one capability — e.g. you only want graceful shutdown.
  • You want to evaluate Nwire piecemeal without committing to the framework.
  • You're building a different framework and want one primitive (the hook layer, the container) without the rest.

When to switch to the full stack ​

If you find yourself reaching for two or three standalone packages, you're likely better off using the full stack — @nwire/app composes these primitives for you and adds Studio, telemetry, topology, and the test harness.

MIT licensed.