@crvouga/mockingbird-service-step-functions

中文文档
3.11.0发布于 2026/11/11MITTypeScriptES Module构建来源已验证近 30 天下载 2269

Stateful AWS Step Functions emulator with idempotent executions, callbacks, deterministic transitions, and history.

原始使用文档
文档目录5 节
  1. Install
  2. Usage
  3. Admin and deterministic controls
  4. Deliberately not modelled
  5. API

@crvouga/mockingbird-service-step-functions

Local emulators. Real API contracts. Part of Mockingbird.

Stateful AWS Step Functions emulator for the official SFN SDK v3 client. It models Standard execution identity, input/output strings, deterministic terminal transitions, callback tokens, stop requests, ordered history, pagination, and shared-clock scripts without contacting AWS.

Install

npm install -D @crvouga/mockingbird-service-step-functions

ESM only. Node 22+ or Bun 1.2+.

Usage

Point the SFN client's endpoint option at the emulator. Fixture SigV4 credentials are accepted.

import { DescribeExecutionCommand, SFNClient, StartExecutionCommand } from "@aws-sdk/client-sfn"
import { createServer } from "@crvouga/mockingbird-service-step-functions/server"

// Test setup: start the emulator with a scripted state machine and point the SDK's endpoint at it.
const server = await createServer({
  stateMachines: [
    {
      name: "jobs",
      scripted: { status: "SUCCEEDED", output: '{"ok":true}', afterMs: 1000 },
    },
  ],
})
const sfn = new SFNClient({
  endpoint: server.url,
  region: "us-east-1",
  credentials: { accessKeyId: "fixture", secretAccessKey: "fixture" },
})

// Application code: the SFN SDK calls it already makes.
const { executionArn } = await sfn.send(
  new StartExecutionCommand({
    stateMachineArn: "arn:aws:states:us-east-1:000000000000:stateMachine:jobs",
    input: JSON.stringify({ id: 1 }),
  }),
)

// Test control: move the emulator clock past the script's `afterMs` instead of sleeping.
await fetch(`${server.url}/__admin/clock`, { method: "POST", body: JSON.stringify({ advance: 1000 }) })

const execution = await sfn.send(new DescribeExecutionCommand({ executionArn }))
console.log(execution.status, execution.output) // SUCCEEDED {"ok":true}

await server.close()

Supported operations are StartExecution, DescribeExecution, StopExecution, GetExecutionHistory, SendTaskSuccess, SendTaskFailure, and SendTaskHeartbeat. Running executions are idempotent by state-machine ARN, name, and exact input. Closed-name reuse and conflicting running input return ExecutionAlreadyExists. JSON input/output remain strings at the wire.

Admin and deterministic controls

  • GET/POST /__admin/state-machines lists or registers compact local definitions.
  • GET /__admin/executions inspects executions with task tokens redacted.
  • GET /__admin/executions/:arn/task-token retrieves a local callback token.
  • POST /__admin/executions/:arn/transition deterministically moves a running execution to SUCCEEDED, FAILED, TIMED_OUT, or ABORTED.
  • Scripted machines transition when the shared clock reaches afterMs; no polling sleep is necessary.
  • Fault presets are throttled and unavailable.

The shared runtime also supplies reset, timeline, journal, metrics, faults, and namespace isolation through x-mockingbird-namespace, /__admin/ns/<name>, or SigV4 access-key mappings.

Deliberately not modelled

The full Amazon States Language interpreter, real service integrations, Express Workflows, IAM evaluation, CloudWatch delivery, production retention limits, dashboards, and billing are not modelled. Definitions can be retained as fixtures, while deterministic scripts and callback tasks cover the current consumer contract.

API

  • StepFunctionsAPI, StepFunctionsAPIOptions, StateMachineSeed: handler and fixtures.
  • Execution, ExecutionStatus, HistoryEvent, StateMachine: durable workflow state.
  • createRuntime, StepFunctionsRuntime, StepFunctionsRuntimeOptions: full Mockingbird runtime.
  • STEP_FUNCTIONS_NAMESPACE, STEP_FUNCTIONS_PRESETS, accessKeyCredential: constants and controls.
  • document, operationIds, supportedOperationIds: generated OpenAPI metadata.
  • createServer, StepFunctionsServerOptions, DEFAULT_PORT, serveTarget from ./server: Node HTTP adapter and CLI integration.

Official oracle: AWS Step Functions API Reference.

版本与发布记录

@crvouga/mockingbird-service-step-functions 共发布 37 个版本,首次发布于 2026/09/23;过去 12 个月发布了 37 个版本。最新版本附带 npm provenance 构建来源证明,可追溯到公开的 CI 构建记录。

版本发布日期距今
3.11.0latest2026/11/11今天
3.10.52026/11/038 天前
3.10.42026/11/038 天前
3.10.32026/11/038 天前
3.10.22026/11/038 天前
3.10.12026/11/038 天前

关于 @crvouga/mockingbird-service-step-functions 的常见问题

@crvouga/mockingbird-service-step-functions 是什么?

Stateful AWS Step Functions emulator with idempotent executions, callbacks, deterministic transitions, and history.

如何安装 @crvouga/mockingbird-service-step-functions?

在项目目录运行 npm install @crvouga/mockingbird-service-step-functions,或使用 pnpm add / yarn add / bun add。它还提供命令行工具 mockingbird-step-functions,可以用 npx mockingbird-step-functions 直接运行。

@crvouga/mockingbird-service-step-functions 支持 TypeScript 吗?

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

@crvouga/mockingbird-service-step-functions 支持 ESM 还是 CommonJS?

以 ES Module 形式发布,推荐使用 import 引入。在 CommonJS 项目中,Node.js 20.19+ / 22.12+ 可以直接 require() 不含顶层 await 的 ES Module,更早的版本需要改用动态 import()。

@crvouga/mockingbird-service-step-functions 可以商用吗?

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

@crvouga/mockingbird-service-step-functions 的下载量有多少?

根据 npm 官方下载统计,@crvouga/mockingbird-service-step-functions 在 2026/10/11 – 2026/11/09 这 30 天内被下载 2,269 次,日均约 76 次。下载量会把 CI 构建、镜像同步和作为其他包依赖的安装一并计入,适合横向比较热度,不能直接等同于使用人数。

@crvouga/mockingbird-service-step-functions 还在维护吗?

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