@expressots/adapter-express

中文文档
4.3.0发布于 2026/09/13MITTypeScriptESM + CJS近 30 天下载 102.1万

Expressots - modern, fast, lightweight nodejs web framework (@adapter-express)

原始使用文档
文档目录10 节
  1. Install
  2. What This Package Does
  3. Quick Look
  4. Requirements
  5. Preview modules
  6. Cloudflare binding providers
  7. Documentation
  8. Contributing
  9. Support the project
  10. License
ExpressoTS

@expressots/adapter-express

Express HTTP adapter for ExpressoTS. Connects the framework core to the Express.js server engine.

npm License Discord Build

Documentation · Getting Started · Project Board · Community


Install

npm i @expressots/adapter-express

What This Package Does

This adapter bridges ExpressoTS Core and Express.js. It provides the HTTP server implementation, route registration, middleware pipeline, and the App class that wires everything together. Install it alongside @expressots/core to run ExpressoTS on Express.

Quick Look

import { AppExpress } from "@expressots/adapter-express";
import { AppContainer, CreateModule, bootstrap } from "@expressots/core";
import { AppController } from "./app.controller";

export class App extends AppExpress {
  private readonly container: AppContainer = this.configContainer([CreateModule([AppController])]);

  async configureServices(): Promise<void> {
    // register middleware, interceptors, error handlers
  }
}

void bootstrap(App); // starts on process.env.PORT or 3000

bootstrap() builds the container, runs the AppExpress lifecycle hooks (globalConfiguration, configureServices, postServerInitialization), starts the HTTP server, and wires graceful shutdown on SIGINT / SIGTERM.

Requirements

  • Express 5 (the adapter targets the Express 5 API; body parsing uses the Express 5 native parsers)
  • Node.js >= 20.19.0
  • @expressots/studio-agent is an optional peer dependency: install it to enable ExpressoTS Studio integration, or omit it with no impact on the adapter.

Preview modules

The micro-api module (gateway, service-mesh, serverless, queue) is preview quality: its APIs may change. Use it for experimentation, not production-critical paths.

Cloudflare binding providers

On Cloudflare Workers, a micro app can resolve its bindings (KV, D1, R2, Queues) through typed tokens instead of reading env by name in every handler:

import {
  cloudflareAdapter,
  cloudflareBindings,
  type CloudflareRequest,
  micro,
} from "@expressots/adapter-express";

interface Env {
  SETTINGS: KVNamespace;
  DB: D1Database;
}

const bindings = cloudflareBindings<Env>();
const Settings = bindings.kv("SETTINGS");
const Database = bindings.d1("DB");

const app = micro<CloudflareRequest<Env>>({ showBanner: false, studio: { enabled: false } });

app.get("/theme", async (req) => ({
  theme: await req.services.get(Settings).get("theme"),
}));

app.get("/items", (req) => req.services.get(Database).prepare("SELECT * FROM items").all());

export default cloudflareAdapter<Env>(app);
  • bindings.kv, bindings.d1, bindings.r2 and bindings.queue return frozen tokens, memoized by kind and name. Tokens carry only a name and a kind, so creating them at module scope is safe on Workers.
  • req.services.get(token) reads the binding from the current request's env every time; nothing is cached across requests. req.services.has(token) reports whether the binding is present. req.cloudflare.env remains available for direct access.
  • A binding absent from env raises CloudflareBindingNotFoundError (code: "EXPRESSOTS_CLOUDFLARE_BINDING_NOT_FOUND"), which flows through the app's error handler like any other error. Inherited object properties such as toString are never treated as bindings.
  • Binding kinds are matched structurally against Cloudflare's runtime interfaces (for example, a KV namespace is recognised by getWithMetadata). With an explicit Env, each factory accepts only the names whose value matches its kind, and a value matching more than one kind is rejected as ambiguous. Without an Env type, any string is accepted, for applications whose bindings are configured dynamically.

The providers are verified inside workerd against Miniflare's KV, D1, R2 and Queue implementations, and a bundle gate keeps their cost under 1 KiB gzip; both run in CI from test/cloudflare-bindings-worker.

Documentation

For guides, API reference, architecture patterns, and examples visit doc.expresso-ts.com.

Contributing

Welcome to the ExpressoTS community. See the Contributing Guide for how to get involved.

Support the project

License

MIT. See LICENSE.

版本与发布记录

@expressots/adapter-express 共发布 35 个版本,首次发布于 2023/09/13;过去 12 个月发布了 12 个版本。

版本发布日期距今
4.3.0latest2026/09/132 个月前
4.2.12026/08/043 个月前
4.2.02026/08/043 个月前
4.1.12026/07/283 个月前
4.1.02026/07/283 个月前
4.0.02026/07/173 个月前

其他发布通道:beta → 3.0.0-beta.4.2,preview → 4.0.0-preview.1,next → 4.0.0-preview.3.4。

关于 @expressots/adapter-express 的常见问题

@expressots/adapter-express 是什么?

Expressots - modern, fast, lightweight nodejs web framework (@adapter-express)

如何安装 @expressots/adapter-express?

在项目目录运行 npm install @expressots/adapter-express,或使用 pnpm add / yarn add / bun add。

@expressots/adapter-express 支持 TypeScript 吗?

支持。包内自带 TypeScript 类型声明(package.json 声明了 types 入口),安装后即可获得类型提示,无需再安装 @types 包。

@expressots/adapter-express 支持 ESM 还是 CommonJS?

同时提供 ES Module 与 CommonJS 入口,import 和 require() 都可以使用,打包工具会自动选择合适的版本。

@expressots/adapter-express 需要什么版本的 Node.js?

package.json 的 engines 字段要求 Node.js >=20.19.0。版本不符时 npm 默认只给出警告,开启 engine-strict 后会拒绝安装。

@expressots/adapter-express 可以商用吗?

@expressots/adapter-express 使用 MIT 许可。宽松许可:允许商业使用、修改和再分发,通常只需在分发时保留原版权与许可声明。以上为概括,不构成法律意见,请以许可原文为准。

@expressots/adapter-express 的下载量有多少?

根据 npm 官方下载统计,@expressots/adapter-express 在 2026/10/14 – 2026/11/12 这 30 天内被下载 1,020,979 次,日均约 34,033 次。下载量会把 CI 构建、镜像同步和作为其他包依赖的安装一并计入,适合横向比较热度,不能直接等同于使用人数。

@expressots/adapter-express 还在维护吗?

最新版本 4.3.0 发布于 2026/09/13(2 个月前);至今共发布 35 个版本,其中过去 12 个月发布了 12 个;首次发布于 2023/09/13。发布频率只是参考信号:功能稳定的工具可能很少需要更新,建议结合源码仓库的 issue 和提交记录判断。