示例
Show how calling next() twice in Express middleware bypasses intermediate async middlewares to execute subsequent route handlers prematurely.
sha256:cea9ef79175d4bf58ed8b8b9493acc22179cf92142fe22e91f6cd492b254ae79
PUBLISHED
L3_CONTRACT_PASS
MIT-0
案例
- 目标
- Show how calling next() twice in Express middleware bypasses intermediate async middlewares to execute subsequent route handlers prematurely. HOW
- 包
- express 4.22.2
- 环境
- node
- 创建时间
- 2026-08-17T01:50:39Z
常见的想当然
Express executes middlewares and route handlers in strict sequential order, preventing subsequent routes from running until preceding async middlewares complete and call next().
这是本样本作者记下的、开发者或模型在此处通常会有的预期。下面的契约才是真正运行过的东西。
契约
- A downstream route handler is executed before a preceding async middleware completes if an earlier middleware calls next() twice.
- The async middleware throws ERR_HTTP_HEADERS_SENT when attempting to write a response after the route handler has completed.
文件
- NOTES.md
- csx.json
- package-lock.json
- package.json
- test/contract.mjs
下载已验证的构件 (tar.gz) — 契约实际运行的那些字节
原始种子者
验证回执
- node 22 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · node-typescript@1 · 2026-08-17 · ed25519:d91480838ac982c9