Get started
Guides
Start from zero and ship your first xTaskjs application quickly.
Open quick startxTaskjs Framework
An original Astra-inspired landing experience for xTaskjs, built around fast onboarding, documentation depth, and production-aware workflows.
Compose HTTP delivery, CQRS, event-driven workflows, queue consumers, realtime gateways, and server-rendered views without leaving the same framework runtime.
Start here
The layout keeps the same default root route but gives it the structure users expect from a framework front page: fast orientation, guided learning paths, and product-style sections.
Get started
Start from zero and ship your first xTaskjs application quickly.
Open quick startUnderstand the runtime
Understand adapters, decorators, value objects, view rendering, and lifecycle hooks.
Browse packagesInspect working apps
Use practical code samples for APIs, jobs, queues, and orchestration.
See samplesWorkflow
This design keeps the same data sources already exposed by the app and reorganizes them into clearer sections for discovery, evaluation, and action.
Open architecture and package docs to understand how adapters, DI, lifecycle, and integrations fit together.
Stay simple with controllers and views, or expand into CQRS, queues, Socket.IO, cache, and event sourcing as the app grows.
Use the official samples and published packages as the shortest route from exploration to production code.
Packages
Published packages are now presented more like a product catalog, closer to the kind of package showcase users expect on a framework homepage.
npm package
Bots integration core for xtaskjs.
Published on npm: Jun 7, 2026, 1:29 PM
npm package
Cache and HTTP caching integration for xtaskjs.
Published on npm: Jun 7, 2026, 1:30 PM
npm package
Commander-based CLI for creating and scaffolding XTaskJS projects.
Published on npm: Jun 7, 2026, 4:06 PM
npm package
Common decorators, validation, and utilities for xtaskjs.
Published on npm: Jun 7, 2026, 1:29 PM
npm package
Typed, fail-fast environment configuration for xtaskjs powered by Zod.
Published on npm: Jun 7, 2026, 1:30 PM
npm package
Core application runtime and DI container for xtaskjs.
Published on npm: Jun 7, 2026, 1:29 PM
npm package
CQRS integration for xtaskjs with read/write datasource bindings.
Published on npm: Jun 7, 2026, 1:31 PM
npm package
Event sourcing integration for xtaskjs with aggregate repositories, lifecycle wiring, and optional TypeORM and queue adapters.
Published on npm: Jun 7, 2026, 1:32 PM
npm package
Express HTTP adapter for xtaskjs.
Published on npm: Jun 7, 2026, 1:32 PM
npm package
Fastify HTTP adapter for xtaskjs.
Published on npm: Jun 7, 2026, 1:32 PM
npm package
Internationalization integration for xtaskjs.
Published on npm: Jun 7, 2026, 1:32 PM
npm package
Mailer integration for xtaskjs.
Published on npm: Jun 7, 2026, 1:33 PM
npm package
MCP server builder integration for xtaskjs.
Published on npm: Jun 7, 2026, 1:33 PM
npm package
Queue integration for xtaskjs.
Published on npm: Jun 7, 2026, 1:31 PM
npm package
Scheduler integration for xtaskjs.
Published on npm: Jun 7, 2026, 1:33 PM
npm package
Authentication and authorization integration for xtaskjs.
Published on npm: Jun 7, 2026, 1:34 PM
npm package
Socket.IO integration for xtaskjs.
Published on npm: Jun 7, 2026, 1:34 PM
npm package
In-memory testing runtime with module graph and DI overrides for xtaskjs.
Published on npm: Jun 7, 2026, 1:35 PM
npm package
Rate limiting (throttler) integration for xtaskjs.
Published on npm: Jun 7, 2026, 1:35 PM
npm package
TypeORM integration for xtaskjs.
Published on npm: Jun 7, 2026, 1:30 PM
npm package
Modern schema-based validation for xtaskjs with Zod or Valibot.
Published on npm: Jun 7, 2026, 1:35 PM
npm package
Value object primitives, converters, and XTaskJS integration helpers.
Published on npm: Jun 7, 2026, 1:36 PM
Ecosystem
Follow updates, contribute modules, and discuss roadmap priorities.
Delivery
Need help in production? Open an issue or collaborate with maintainers.
Newsroom
Recent releases, documentation work, and framework changes stay visible from the homepage instead of being buried behind navigation.
Published updates will appear here as soon as the admin posts them.
Next step
The application already opens on the root route, so this redesign becomes the default experience automatically when the project starts.