Providers
Dependency packages re-exported by Codexa Core, including JetRouter, so a project never installs or maps them separately.
Codexa Core uses JetRouter for HTTP route matching alongside several third-party packages. These dependencies are re-exported through @codexa/core/providers, so a project can use the same versions as Codexa Core without installing and configuring each one separately.
import { MongoClient } from '@codexa/core/providers/mongodb';
import { zod } from '@codexa/core/providers/zod';
import Redis from '@codexa/core/providers/ioredis';Two ways to import a provider
A dedicated subpath, @codexa/core/providers/<name>, gives the full package surface directly, exactly as if you had installed it yourself.
import { zod } from '@codexa/core/providers/zod';
import { createRouter } from '@codexa/core/providers/jetrouter';The providers namespace subpath gives every provider as a named export instead, useful when you want several of them from one import line.
import { zod, mongodb, ioredis, jetrouter } from '@codexa/core/providers';
const client = new mongodb.MongoClient(uri);Reach for the dedicated subpath in most code, it is what every example on this site uses. The namespace form mainly helps when writing a small script that touches several providers at once.
What is re-exported
| Subpath | Package | Notes |
|---|---|---|
@codexa/core/providers/path | @std/path | |
@codexa/core/providers/zod | @zod/zod | Also exports zod as an alias for Zod's z namespace, and ZodInfer, ZodInput, ZodOutput, AnyZodObject type helpers |
@codexa/core/providers/dotenv | @std/dotenv | Backs loadEnv's .env file loading |
@codexa/core/providers/ioredis | ioredis | The client type behind createRedisConnection |
@codexa/core/providers/mongodb | mongodb | Includes ObjectId, see Database (MongoDB) |
@codexa/core/providers/qs | qs | Backs parseQueryParams |
@codexa/core/providers/jetrouter | jetrouter | The zero-dependency routing engine the HTTP layer uses to match methods and URL pathnames |
@codexa/core/providers/ua-parser-js | ua-parser-js | Backs parseDevice |
@codexa/core/providers/noble-hashes | @noble/hashes | Backs blake2bDigest, exported as several submodule namespaces since the package has no single root module |
@codexa/core/zod also exists as a shorter compatibility alias for @codexa/core/providers/zod. New code should prefer the full providers/zod path.
JetRouter and Codexa routers
@codexa/core/providers/jetrouter exposes the standalone JetRouter engine, including Router, createRouter, addRoute, findRoute, and routeToRegExp. Its createRouter() creates a method/path matcher.
Use createRouter from @codexa/core/http when you want a reusable collection of Codexa routes to mount into a plugin. Codexa compiles its internal JetRouter matcher during boot and whenever runtime route controls rebuild the route table.
Why this exists
Two problems this avoids: a version of mongodb in your deno.json drifting out of sync with the one Codexa Core itself was built and tested against, and having to separately install and pin every dependency Codexa Core already needs internally, just to get its types.