Skip to content

chore(api): sync barrel exports across api package - #2178

Draft
yassinedorbozgithub wants to merge 1 commit into
mainfrom
chore/api-sync-barrel-exports
Draft

chore(api): sync barrel exports across api package#2178
yassinedorbozgithub wants to merge 1 commit into
mainfrom
chore/api-sync-barrel-exports

Conversation

@yassinedorbozgithub

Copy link
Copy Markdown
Collaborator

Summary

Syncs the barrel files across packages/api/src so that every module's public
symbols are actually re-exported from the package root. Adds two missing barrels
(health/index.ts, mcp/index.ts) and wires them into src/index.ts, plus ~90
previously unexported symbols across audit, extensions, workflow,
transfer, utils, helper, user, i18n, websocket, bindings, and
database. Export-only change — no runtime logic was touched.

Why

@hexabot-ai/api ships a single root entrypoint (exports: { "." : ... }), so
the barrel files are the public API surface for extension authors. Modules
added over recent PRs (MCP tokens, health service, sqlite-vector/pgvector RAG
stores, audit exporters and interceptors, workflow contexts/seeds/schemas,
transfer adapters) landed without their barrel entries, leaving them
unreachable to consumers of the published package.

How to review

Validation

  • pnpm --filter @hexabot-ai/api build — TypeScript compiles and dist/index.d.ts
    resolves all new re-exports.
  • pnpm --filter @hexabot-ai/api lint
  • pnpm --filter @hexabot-ai/api test
  • No behavioral change expected: diff is additive export * from lines only
    (git show --stat → 15 files, 178 insertions, 0 deletions).

@yassinedorbozgithub yassinedorbozgithub self-assigned this Jul 30, 2026
@yassinedorbozgithub
yassinedorbozgithub marked this pull request as draft July 30, 2026 09:14
@yassinedorbozgithub yassinedorbozgithub added the WIP Work in progress label Jul 30, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

WIP Work in progress

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant