Package Map
Use package map with the current published Askr packages.
@askrjs/askr0.0.59
How to use package map
Import only the entrypoint that owns the API. Use generated reference pages for exact signatures and this guide for behavioral constraints.
- Import the published @askrjs/askr entrypoint.
- Keep package map configuration next to the component, route, or server composition root that owns it.
- Handle pending, unavailable, cancellation, and failure states, then verify the production path.
import * as api from '@askrjs/askr';
// Stay on the published entrypoint instead of reaching into dist/ or src/.
const availableExports = Object.keys(api);Runtime packages
@askrjs/askr is the core: `state()`, `derive()`, `selector()`, `defineScope()`/`readScope()`, the JSX runtime, and app startup helpers under its /boot, /router, /resources, /data, /fx, and /testing subpaths. Auxiliary runtime concerns — timing helpers, async resources, query caching — live as subpath exports on this same package rather than as separate installs.
Server packages
@askrjs/server hosts HTTP handling, middleware, routing, auth integration, MCP support, and OpenAPI generation behind subpaths like /http, /middleware, /router, /mcp, and /openapi. @askrjs/node and @askrjs/auth sit alongside it for Node-specific adapters and JWT/OIDC auth flows respectively.
UI packages
@askrjs/ui ships headless, unstyled primitives — button, dialog, select, table, and so on — with no visual opinion baked in. @askrjs/themes wraps most of those primitives with a styled, ready-to-use component per subpath (accordion, card, tooltip, etc.), plus a default token stylesheet at @askrjs/themes/default/tokens.css.
Tooling packages
@askrjs/vite provides the build integration (with a /server subpath for SSR dev tooling), @askrjs/cli scaffolds and runs projects, and @askrjs/schema, @askrjs/i18n, @askrjs/otel, @askrjs/logos, @askrjs/lucide, @askrjs/monaco, @askrjs/fetch, and @askrjs/charts round out validation, localization, telemetry, icons, editor embedding, HTTP client, and charting concerns as separate installs.