Yes, yet another DI library for TypeScript.

A few things kept bothering me about the existing ones, in order of how much they hurt.

- *Type safety requires a special dance.* InversifyJS has ServiceIdentifier<T>, but it is really easy to break the typing. TypeDI tokens are untyped strings. NestJS suffers mostly same, unless you use full classes as dependency tokens. TSyringe infers from constructor metadata, but all of it relies on legacy "reflect-metadata" and decorators mechanism that (a) is soon to be gone, (b) requires additional wiring.

- *Async leaks into callers.* InversifyJS has container.getAsync() for providers that might have been initialized asynchronously. That means every call site needs to know whether what it's asking for was async. The complexity never stays contained. NestJS again gets this right: await everything at bootstrap, then get() is always synchronous. Initialized means ready.

- *Wiring is imperative.* InversifyJS has you call manually .bind(Token).to(Implementation) for every provider. It works, but it's ugly. NestJS figured out the right answer: declare what a module owns, what it needs, what it exposes, and let the container figure the rest out. That declarative model is the thing I wanted most, but it comes with an entire framework. NestJS gets hairy when your single app starts accepting just Nats JetStream in addition to HTTP.

- *reflect-metadata.* Every major TS DI library runs on TS "experimentalDecorators" plus a global runtime polyfill for TypeScript metadata. TC39 Stage 3 decorators shipped in TypeScript 5.0, and are soon to be natively supported in JS engines. No flags, no polyfills.

Ampulla is my attempt at fixing all four: injection<T>() tokens that carry their type intrinsically, a declarative @Module/@Injectable model lifted straight from NestJS, async-safe bootstrapping where container.get() is always synchronous, and TC39 decorators throughout.

It's intentionally just a DI container, not a framework. There is no HTTP server, no router, no CLI included. Optional adapters for Hono and H3 are included but tree-shakeable. The whole npm package has zero runtime dependencies.

Very early, 1.0.0 published just today. DI is not the most popular topic on HN, but existing DI in TypeScript is annoying enough that I had to publish something new.

GitHub: https://github.com/ukstv/ampulla | npm: npm install ampulla

Autology: Writing a self-rewriting Lisp (Lambda Days)

Show HN: Hardwood 1.0: A Fast, Lightweight Apache Parquet Reader for the JVM

From Emacs to Cursor, the end of your IDEs is near

Anthropic says Alibaba used 25k accounts to mine Claude

Show HN: Ampulla: Modern TypeScript DI with NestJS Ergonomics

It's 1996 All over Again on the New GIMP 0.54 Flatpak

I owe my life to a 1913 road rage incident

What Is a File Format?

Australian rescue team uses AI-powered drone to find lost hikers [video]

Remediation Asymmetry: When Agents Can Diagnose More Than They Can Fix

Catch silent Meta/TikTok CAPI failures before they tank your matching

Native Hacker News TUI client with AI comments summary written in Golang

Org Novelist

Engine Simulator – Community Edition

Show HN: Luma – A New Workspace for Frida

Legion LegalTech sues U.S. over Anthropic Fable 5 and Mythos 5 shutdown

Non-Existent or Intermittent Internet Access When Using FusionAuth (2025)

Apple seeks to buy memory chips from blacklisted Chinese company

The PM's Guide to Managing AI Debt

You've tried DuckDuckGo and Brave Search, now get serious with SearXNG

Liquid-Cooling a TE Connectivity 800V DC Busbar and More from the Wiwynn Booth

Text Files as a User Interface

Show HN: HotFX Pseudorandom – value noise in a CSS variable via custom element

Passkey Central

Microsoft extends free Windows 10 security updates until October 12, 2027

Show HN: Ocarina – Automate and test MCP servers from YAML, no LLM

The State has entered the Model Loop

Back to the good old times – Win 7 for Debian (2024)

Distributed LLM Inference with LLM-d

Double threat to privacy: Chat Control 1.0 and 2.0 are back

Ask HN: Are you running production workloads in Pytorch eager mode?