Broken out from #1793.
Scope
- Rename
@ensnode/ensnode-sdk → @ensnode/sdk
- Invert dependency:
@ensnode/sdk depends on enssdk (not the other way around) for shared types
- Consolidate
@ensnode/ensrainbow-sdk as a subpath export of @ensnode/sdk
- Consolidate
@ensnode/ensdb-sdk as a subpath export of @ensnode/sdk
- Establish
@ensnode/sdk/internal subpath for implementation details shared between ENSNode services
From #1793:
@ensnode/sdk — operator-focused ENSNode-specific exports
- depends on
enssdk for shared types
@ensnode/sdk/internal — internal-only shared types/libs between ENSNode services
Context — Omnigraph API evolution
In the short term, APIs like Registrar Actions and Tokenscope may be surfaced within the Omnigraph directly (the current ENSv2 plugin already slightly overlaps with these). In the long term, the Omnigraph may encompass all ENSNode APIs, potentially offering 100% feature parity between a GraphQL surface and an equivalent HTTP/JSON surface. We're not close enough to propose specifics on the unified API yet, but the subpath structure of enssdk is designed to accommodate this evolution.
Breaking changes are acceptable — no transition period required.
Broken out from #1793.
Scope
@ensnode/ensnode-sdk→@ensnode/sdk@ensnode/sdkdepends onenssdk(not the other way around) for shared types@ensnode/ensrainbow-sdkas a subpath export of@ensnode/sdk@ensnode/ensdb-sdkas a subpath export of@ensnode/sdk@ensnode/sdk/internalsubpath for implementation details shared between ENSNode servicesFrom #1793:
Context — Omnigraph API evolution
Breaking changes are acceptable — no transition period required.