obix-binding-oop

Previous name: @obinexusltd/obix-binding-oop — OBIX packages are named without an npm scope since decision D-102 (2026-09-29); the package, its version and its exports are unchanged.

Compatibility package. obix-binding-oop is kept so that code and documents that import it keep resolving. It contains no logic: every export below is the export of obix-core-oop under the old name. New code should import from obix-core-oop.

Old package: recovery-era:[email protected] (commit af124db; never published). Decision: rename (recovery-era name; listed in obix-naming.json (OBIX monorepo record) legacyShims) in docs/recovery/migration-table.md (OBIX monorepo record) — canonical name of the previous recovery iteration (commit af124db), never published; the implementation moved from binding/ into core/, the old name is kept as a compat shim so the workspace's own consumers keep resolving.

obix-binding-oop

| Old name | Is | |---|---| | toOOP | obix-core-oop.toOOP |

Types: OOPConstructor, OOPInstance.

Verification

test/shim.test.mjs imports both packages and asserts, for every entry point: each old name is identical (===) to the owner's export (or, for the derived renderX, behaves as renderWith(createX)); the shim exports exactly these names and nothing else; every excluded name is absent. Verified on Node 26.7 only.

Installation

npm install obix-binding-oop

Basic usage

// existing code keeps working under the old name…
import { toOOP } from 'obix-binding-oop';
// …new code imports the owner: obix-core-oop

API surface

• obix-binding-oop — 1 value export: toOOP
• Type declarations: ./dist/index.d.ts (and a declaration next to every JS entry point).

Architecture role

obix-binding-oop is a compatibility package: it keeps an old name resolving and contains no logic — every export is the export of obix-core-oop. New code imports from obix-core-oop (or from the umbrella obix).

The architecture of OBIX — the package families and which packages are public API — is indexed in the umbrella: docs/architecture.md.

Package relationships

• Depends on (OBIX): obix-core-oop.
• Used by (OBIX): no other OBIX package.

Testing

• 1 test file ships in the npm package (test/): the evidence of the package's contract, published so that its verification can be inspected — not runtime code (no entry point reaches it).
• Standalone: 1 of 1 — it reads nothing outside the package.
• Run them with npm test (node --test "test/*.test.mjs") in the OBIX monorepo, which provides the test tooling (Node's test runner, TypeScript) and the harness.

Documentation

• CHANGELOG.md
• The OBIX architecture index: obix/docs/architecture.md

Repository

• https://github.com/obinexus/obix-binding-oop — [email protected]:obinexus/obix-binding-oop.git
• Issues: https://github.com/obinexus/obix-binding-oop/issues
• The repository is a clean export of the package from the OBIX monorepo. Its lineage — the sources it was recovered from and its earlier names — is PROVENANCE.json, shipped in this package; the repository's copy also records the monorepo commit it was exported from.

License

MIT — see LICENSE.