Skip to content

Make @wavehouse/sdk consumable outside the monorepo (npm publish or git-installable) #227

Description

@EricAndrechek

Area: sdk — friction (DX) · found via WaveHouse-Stats dogfooding

Expected: depend on @wavehouse/sdk from another repo (our Worker + admin/reconciler CI) to dogfood it.

Actual: it isn't on npm, and npm/pnpm install github:Wave-RF/WaveHouse won't resolve a package nested in clients/ts. package.json is publish-ready (publishConfig.access: public, prepare build, files: ["dist"]) but no release has been cut. Consuming it today means clone + build + pack/link — non-trivial in CI.

Impact (Stats): we fall back to raw HTTP (/v1/admin/*) and will adopt the SDK once it's installable.

Scope: publish to npm (even a prerelease) or make it git-installable. Also confirm the SDK surface includes admin raw-SQL/DDL, not just policy.ts.

Related: SDK feature epic #194 (this consumability step isn't in its checklist); first publish would naturally ride the v0.1.0-alpha.1 release (#149).


From WAVEHOUSE-FEEDBACK.md (WaveHouse-Stats dogfooding); validated by code-read against 0f8826c on 2026-06-04.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/infraCI, build, deploy, Docker, releasearea/sdkTypeScript SDK (clients/ts/)enhancementNew feature or request

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions