lib.plugins

@lssm-tech/lib.plugins

Website: https://contractspec.io

Plugin API and registry for ContractSpec extensions.

What It Provides

• Layer: lib.
• Consumers: bundles, CLI.
• Related ContractSpec packages include @lssm-tech/lib.contracts-spec, @lssm-tech/lib.schema, @lssm-tech/tool.bun, @lssm-tech/tool.typescript.
• Related ContractSpec packages include @lssm-tech/lib.contracts-spec, @lssm-tech/lib.schema, @lssm-tech/tool.bun, @lssm-tech/tool.typescript.

Installation

npm install @lssm-tech/lib.plugins

or

bun add @lssm-tech/lib.plugins

Usage

Import the root entrypoint from @lssm-tech/lib.plugins, or choose a documented subpath when you only need one part of the package surface.

Architecture

• src/config.ts is part of the package's public or composition surface.
• src/index.ts is the root public barrel and package entrypoint.
• src/registry.ts is part of the package's public or composition surface.
• src/types.ts is shared public type definitions.

Public Entry Points

• Export . resolves through ./src/index.ts.
• Export ./config resolves through ./src/config.ts.
• Export ./registry resolves through ./src/registry.ts.
• Export ./types resolves through ./src/types.ts.

Local Commands

• bun run dev — contractspec-bun-build dev
• bun run build — contractspec-bun-build build
• bun run test — bun test --pass-with-no-tests
• bun run lint — bun lint:fix
• bun run lint:check — biome check .
• bun run lint:fix — biome check --write --unsafe --only=nursery/useSortedClasses . && biome check --write .
• bun run typecheck — tsgo --noEmit
• bun run publish:pkg — bun publish --tolerate-republish --ignore-scripts --verbose
• bun run publish:pkg:canary — bun publish:pkg --tag canary
• bun run clean — rimraf dist .turbo
• bun run build:bundle — contractspec-bun-build transpile
• bun run build:types — contractspec-bun-build types
• bun run prebuild — contractspec-bun-build prebuild

Recent Updates

• Replace eslint+prettier by biomejs to optimize speed.

Notes

• Plugin interface is a public API contract — breaking changes affect all published plugins.
• Registry must stay backward-compatible; older plugin manifests must remain loadable.
• Config schema changes require a migration path for existing plugin configurations.