Create

Sign in to ReadmeX

or

How we handle your data: Privacy Policy

ReadmeX

Your AI reading companion

What would you like to catch up on?

Pick a briefing, or ask your own question.

Your community and people briefings stay personal to you.

cordis

cordis: A meta-framework for spatiotemporal composability.

What problem it solves

Applications often need to combine services, plugins, configuration, and runtime behavior while preserving clear boundaries between components. Cordis addresses composability through contextual services, interception, configuration validation, and lifecycle-aware runtime behavior.

Key features

  • Service composition and interception — Services can participate in contextual composition, with metadata merging and service lookup boundaries supported by the core framework.

    Source: packages/core/README.md, packages/core

  • Configuration validation and diagnostics — Configuration errors can identify the source location that caused them, including entry option fields and YAML or JSON syntax problems.

    Source: packages, packages/loader

  • Runtime lifecycle management — The runtime handles concurrent execution and disposal states, including identifying the failing event in aggregate errors and settling disposed fibers.

    Source: packages/core/README.md, packages/core

  • Hot module replacement — The hot module replacement tooling handles configuration and path changes while excluding nested dependency and dot-path directories on Windows.

    Source: packages, packages/hmr

  • TypeScript and NodeNext support — Type declarations use explicit file extensions, allowing projects that use the NodeNext module resolution mode to consume them without related errors.

    Source: packages/core/README.md, tsconfig.base.json

Who it may suit

This may suit developers building extensible applications or plugin systems that rely on contextual services, configuration-driven modules, and lifecycle-aware behavior.

Topics to discuss

  • Which contextual composition patterns should be documented as recommended usage?

  • How should developers configure service boundaries and interception across isolated contexts?

  • Which configuration validation and error-location workflows should receive more examples?


Written by ReadmeX AI from the project's README, source and public GitHub data; it may contain mistakes.

Read the original README https://github.com/cordiverse/cordis#readme

ReadmeX opened this community for a trending project; it is not run by the project. Maintainers can claim it from the community page.

github.comhttps://github.com/cordiverse/cordis

Comments

…