Public API entry points
This guide targets @tagna/udiot@1.0.0-rc.1. Use only paths in the package's
export map. A file appearing under dist/ does not make it a public import.
| Import | Intended use |
|---|---|
@tagna/udiot |
Mixed root surface: pipelines, DI, state, configuration, caching, components and more |
@tagna/udiot/browser |
Browser-oriented state and UI |
@tagna/udiot/database |
Server database adapters/repositories |
@tagna/udiot/database/browser |
Supabase/Firebase browser helpers |
@tagna/udiot/mfe |
Micro-frontend mounting and shared platform context |
@tagna/udiot/platform |
Tenant resolution and scoped services |
@tagna/udiot/node |
Node-oriented root and sandbox exports |
@tagna/udiot/dev |
Development/HMR tooling |
@tagna/udiot/ssg |
Experimental static generation |
@tagna/udiot/web |
Typed web app/page/build/server integration |
@tagna/udiot/server |
Express adapters, request scope and HTTP helpers |
@tagna/udiot/telemetry |
Metrics, traces, logs and run events |
@tagna/udiot/agents |
LLM clients, runners, loops and tools |
@tagna/udiot/sandbox |
Workspace filesystem and sandbox clients |
The ./ssg/* wildcard also exposes matching built files. Prefer the explicit
/ssg entry; wildcard paths are experimental, not a general deep-import policy.
Values versus types
See the generated export inventory for names, value/type status
and candidate/experimental classification. Installed .d.ts declarations are
the exact signature reference for your installed version. Import types with
import type; a type-only declaration is not a runtime constructor.
The root Middleware is a type, not the internal middleware decorator.
Context is a reactive value class, not a middleware parameter decorator.
Use ComponentDecorator for the DI component decorator; the root Component
name is an interface. Root legacy reflection/schema/module type exports do not
expose their implementations as JavaScript values.
There are no separate public /ssr, /isr, /types, /middleware, /state,
/ui, /config, /testing or /runtime/environment entry points.
Use the documented exported names from an appropriate explicit entry point.
Runtime and support
Use ESM on Node >=22.17.0. For browser bundles use the browser-specific entry points and validate the resulting bundle. Root imports are not a browser-safety guarantee. See support levels, installation and TypeScript setup.