@jumentix/runtime-infra

Infrastructure helpers used while compiling and running adapter runtimes.

What it is

Infrastructure helpers used while compiling and running adapter runtimes.

Why it exists

Low-level runtime utilities were duplicated across adapters.

When to use: Working inside backend adapter composition (with bootstrap).

When not to use: Building UI features or offline IndexedDB features.

Responsibility in context

• Stack layer: runtime / infrastructure helpers
• Problem boundary it owns: Runtime infrastructure compiler utilities.
• Used with: adapter-runtime-bootstrap and adapter docs.
• Typical composition: Used under the hood by backend composition.
• Journeys: Runtime contracts reference after REST guide.
• Not responsible for: Business use-cases or SDK HTTP calls.

Prerequisites

• Bun 1.3.13+ (monorepo pin) or the Node runtime your service already uses
• Read Getting started first
• Basic TypeScript modules/import knowledge

Glossary

• Port — TypeScript contract the application depends on (no vendor types).
• Adapter — Concrete implementation that talks to a driver, broker, or protocol.
• Composition root — Process startup code that wires env → adapters → use-cases.

Numbered steps

1. Install

Consumed via backend-template / monorepo composition.

2. First success (under 30 min)

// Juniors rarely import this directly.
// Learn it after you can boot backend-template via the REST guide,
// then inspect how composition uses runtime helpers.

3. Core workflows

1. Follow REST guide first

Get a service running before digging here.

2. Read with bootstrap

Treat this as a support package under adapter-runtime-bootstrap.

3. Avoid UI imports

Never bundle into SPA code.

4. Full practical surface (exports)

• (see package barrel — runtime infra helpers)

Use exports from application/adapters layers as described above — not from domain entities.

Common errors

Verify success: the first-success snippet runs (or typechecks against your service) and your use-case depends only on ports.

Junior checklist (“I can …”)

• I know this supports backend composition only
• I can find the next learning step (adapters / REST guide)

Next step

Continue with Adapters hub.