Reference
Package exports
Find the import path for a core API or integration package.
On this page
Import contract helpers such as route() from @hulla/api. Import client and server APIs from their separate entrypoints below. Each integration package is listed with its purpose and documentation.
| Entrypoint | Primary exports |
|---|---|
@hulla/api/client | createClient, clientMiddleware, clientRouteIntegration, client/transport/result types |
@hulla/api/server | defineServer, createServerAdapter, serverContextAdapterId, server middleware/context/handler types |
@hulla/api/fetch | fetchTransport, fetchAdapter, createFetchHandler, Fetch boundary types |
@hulla/api/in-process | inProcessTransport, inProcessAdapter |
@hulla/api/stream | ndjson, sseJson, stream format and response helpers |
@hulla/api/errors | isAPIError, toAPIProblem, annotateAPIErrorIssues, operational error types |
@hulla/api/validation | codec, schema execution helpers, Standard Schema-related types |
@hulla/api/compiler | compileContract, freezeCompiledRoutes, compiled manifest types |
@hulla/api/adapters | Advanced route executor, representation readers/writers, adapter response types |
Every host integration is a separate package so client bundles do not retain framework or Node dependencies. Packages with distinct runtime surfaces use explicit subpaths: @hulla/api-next/client and /server, @hulla/api-nuxt/client and /server, @hulla/api-sveltekit/server and /remote, @hulla/api-cloudflare/pages, and @hulla/api-node/http.
Use the relevant integration guide for its mounting function and native context types. Application code should prefer the smallest public entrypoint that owns the capability it needs; consult the package declarations for the complete symbol inventory.
@hulla/api-control adapts each typed client call to a resolved Result, while preserving the route’s success and declared-error response types. See Result-returning clients for the complete setup, failure categories, and query-library tradeoff.