Skip to content

API Reference ​

Reference for the checked-in @azure-net/kit 6.0.0-next.16 and @azure-net/tools 2.1.0 sources. Package entry points, not every source-file export, define the public API. Svelte >= 5.57.1 and SvelteKit >= 3.0.0 are peer requirements.

ImportReference
@azure-net/kitSvelte, shared services, bootstrap API
@azure-net/kit/deliveryAsync helpers and presenters, schemas and all validation rules
@azure-net/kit/infraHTTP, datasource, DTO mapping, responses, queries
@azure-net/kit/errorsErrors
@azure-net/kit/toolsTools reexports
@azure-net/kit/server-contextRequestContext
@azure-net/kit/pluginPlugin API
@azure-net/kit/i18nTranslation API
@azure-net/kit/internal/serverInternal integration entry

Public export inventory lists every runtime symbol and exported type by entry point. Exact signatures preserves overloads, option interfaces, class members and supporting types from TypeScript declaration emission.

For setup and lifecycle wiring, use Bootstrap. For locale loading and hydration, use Translations. These API pages describe contracts, not a second setup guide.

Runtime boundaries ​

  • Construct reactive helpers during component initialization or an owned Svelte effect scope. Do not put user-specific reactive state in server module globals.
  • Register containers and presenters at module scope, but resolve server instances inside an active plugin-managed request.
  • RequestContext.current(), server cookies and server HTTP calls require that request scope. There is no public manual context setter.
  • server: true signals use Svelte hydratable; await them during component initialization and return serializable data. They are not a replacement for server-only modules.
  • Tools that touch browser storage or DOM do not gain SSR capability merely by being reexported from kit.