Foundation · 2026-07-08
From internal system to installable tool.
The first public npm release made Opus usable where it matters: in another team's application.
The beginning of the library as a dependable external package, with its own build, styles, declarations, and consumer documentation.
A package with a real contract
The public package shipped transpiled code, CSS, TypeScript declarations, package metadata, and a release workflow designed for consumers rather than the monorepo alone.
Dogfooding the release
The marketing application switched to consuming the published npm package, making the project's own site a practical consumer of every release.
A direction, not just a distribution
That release established the groundwork for a component library that can keep growing without losing the traceability and quality expected by production teams.