cordiverse/cordis

What it does

Cordis is a TypeScript meta-framework built around what its authors call spatiotemporal composability: plugins are loaded into a running service and can be replaced or reconfigured at runtime. The repository is tagged effect, framework, nodejs and plugin, and the design centers on an in-runtime inversion-of-control container, so a running application can swap code underneath itself while continuing to execute.

The project is explicitly under active development, and the API is not yet stable and may change without notice. The companion paper, A Programming Paradigm for Spatiotemporal Composability, is on arXiv with a paper repository.

Cordis suits developers building extensible Node.js applications where plugins need to be loaded, versioned and reconfigured without restarting the host, and researchers or advanced users interested in runtime IoC designs.

Getting started

The README does not include an installation command, a package name, or a minimal runnable example, so a complete first-run flow cannot be reproduced from the provided material. The gaps are: package installation, entry-point setup, and how to register a first plugin.

The official documentation entry point is the cordis-primer, which is still under construction. Start there to find the current installation and API guidance. The repository is the place to check for the source and any examples, since the README itself is a short landing page rather than a guide.

Constraints

• API instability: the README states the API may change without notice, so pin versions in anything you ship and expect breaking changes.
• Documentation maturity: the official docs are described as still under construction, so some behaviors may need to be read from the source.
• Runtime scope: the design is aimed at Node.js plugin architectures with runtime IoC, as reflected in the repository topics; it is not a general-purpose UI or application framework.
• Plugin versioning: an HN commenter raises possible "dll hell" when two plugins depend on different versions of the same plugin (discussion), a concern worth checking against the design for any plugin-heavy deployment.
• License: MIT.

HotRepo's take

The project appeared on the all-language GitHub daily list in mid-August 2026 with 616, 719, 959 and 957 stars gained on 15–18 August, then appeared on the TypeScript daily list on 5 November 2026 at position 9 with 55 stars gained. The HN thread from 13 August 2026 drew only 2 points and 1 comment, so the star growth is not matched by discussion volume there.

The one substantive HN comment likes the in-runtime IoC approach as a fit for agents changing code underneath a running system, but flags plugin version conflicts as a possible weak point (comment). Given the unstable API and unfinished docs, Cordis currently reads as something to evaluate at the source level rather than adopt as a stable dependency, and the single observed TypeScript ranking is not enough to judge a sustained trend.