How Devflare wires Pipelines from config to runtime
Pipelines bindings let Workers send event records into Cloudflare-managed ingestion pipelines.
Pipelines compiles from to Wrangler , with local/test behavior called out explicitly.
Use this page when you need emitted config, preview behavior, or Cloudflare-specific limits. The overview and example pages stay focused on everyday app code.
- Normalization
- Devflare normalizes before emitting Wrangler
- Compile target
- Wrangler
- Preview note
- Devflare records local sends but does not create pipelines, manage R2 sinks, or emulate production batching.
How authored config becomes Wrangler config
The authored config stays camelCase and project-oriented. The compiler translates that into the Wrangler keys Cloudflare expects.
The emitted output is shown here so the usage pages do not have to explain compiler details.
Pipelines config and emitted Wrangler output
Use this when you need to check how the Devflare config becomes Wrangler-compatible config.
What local runtime support covers
- Offline-native for send-recording tests; Cloudflare owns production batching and sink delivery
- The default docs recipe uses or .
- Pure unit tests can use / when the test only needs deterministic application behavior.
Compile, preview, and cleanup behavior
- Devflare emits Wrangler from the native config surface.
- Preview and deployment lifecycle stay feature-specific; do not assume all Cloudflare products can be created, cloned, or cleaned up the same way.
- Devflare records local sends but does not create pipelines, manage R2 sinks, or emulate production batching.
Cloudflare docs vs the Devflare layer
Cloudflare Pipelines docs is the platform reference. Use this internals page when you need to compare Cloudflare's product docs with Devflare config, generated env types, local support, and preview behavior for .
| Question | Cloudflare docs | This Devflare page |
|---|---|---|
| Primary focus | Platform reference for sending records from Workers into Cloudflare Pipelines. | How to author , what the runtime surface looks like, and how Pipelines fits a Devflare project. |
| Testing and runtime lens | Cloudflare’s docs focus on the raw binding API, product semantics, and platform limits for the binding itself. | Offline-native for send-recording tests; Cloudflare owns production batching and sink delivery. Use the Devflare guidance when you need the honest local harness or the right remote gate instead of only the product API shape. |
| When to open it | When you need the platform contract, limits, APIs, or account-level product details. | When you are wiring, testing, previewing, or reviewing the binding inside a Devflare app. |
Previous
Pipelines
Add the Pipelines config, call from worker code, and start with the local test path Devflare supports.
Next
Testing Pipelines
Test Pipelines by choosing the local harness that matches the product boundary instead of reaching for Cloudflare by default.