Live
Embedding Vercel’s Zig Coding Agent: Architecture and Ops ImpactGemini 4 Argon trims ADK session prep and import latency by up to 40%Rethinking CI/CD: The Sensor Limits of an Agentic Software FactoryResolving the Kubernetes Autoscaling Conflict: Independent Controllers vs. Autonomous CoordinationAI‑Generated Queries Move Data Interface to Embedded DuckDB for Disaster‑Recovery AnalyticsIntegrating NVIDIA Earth-2 StormScope EU: Architecture, Ops, and Security TakeawaysData Agent Kit GA introduces open‑source skills and split guardrails for agent‑driven data accessTLS certificate authority eMudhra exits market after weak intermediate keys expose supply riskEmbedding Vercel’s Zig Coding Agent: Architecture and Ops ImpactGemini 4 Argon trims ADK session prep and import latency by up to 40%Rethinking CI/CD: The Sensor Limits of an Agentic Software FactoryResolving the Kubernetes Autoscaling Conflict: Independent Controllers vs. Autonomous CoordinationAI‑Generated Queries Move Data Interface to Embedded DuckDB for Disaster‑Recovery AnalyticsIntegrating NVIDIA Earth-2 StormScope EU: Architecture, Ops, and Security TakeawaysData Agent Kit GA introduces open‑source skills and split guardrails for agent‑driven data accessTLS certificate authority eMudhra exits market after weak intermediate keys expose supply risk
Cloudflare

Miniflare v5 introduces new config model and removes legacy APIs for cf CLI readiness

Ninja·September 8, 2026·2 min read·via Cloudflare Developer Platform
AI SummaryPowered by AI

Miniflare v5 changes its configuration format to match cloudflare.config.ts and drops several deprecated and internal APIs. The shift forces developers and operators to rely on higher‑level tools and adjust local testing setups, directly impacting CI pipelines and debugging workflows.

Miniflare v5 updates its configuration schema to follow cloudflare.config.ts and removes a set of legacy and internal APIs. The changes are relevant for anyone using local Workers development tools because they alter how projects are configured, how modules are discovered, and how local persistence is handled.

New configuration shape

The primary alteration is a restructured configuration object that mirrors the programmatic cloudflare.config.ts format now supported for testing. Projects that previously supplied Miniflare‑specific config files must migrate to the new shape to stay compatible with the upcoming cf CLI.

Removed and relocated APIs

  • Deprecated bindings such as the legacy alpha D1 bindings are no longer available.
  • Internal helpers like wrappedBindings have been eliminated.
  • Miniflare no longer performs its own module discovery; callers (e.g., Wrangler, the Vite plugin) must provide the module graph.
  • Routes that were only reachable locally under /cdn-cgi are now nested under /cdn-cgi/local.
  • Per‑resource persistence flags have been replaced by a shared persistence root option.

Effect on existing tooling

Most developers already rely on higher‑level wrappers—wrangler dev, the Cloudflare Vite plugin, or @cloudflare/vitest-plugin. Those wrappers have been updated to emit the new configuration shape, so projects that use them should see no immediate breakage. Direct consumers of Miniflare will need to adjust imports, drop removed APIs, and align their local testing scripts with the new persistence model.

Related CloudNinjas coverage: hands-on guides.

What This Means For Practitioners

Review any custom Miniflare usage for the removed APIs and update configuration files to the cloudflare.config.ts layout. Verify that your CI pipelines invoke the higher‑level tools rather than Miniflare directly, as the tools now handle module graph generation. Pay attention to the relocated /cdn-cgi/local routes when writing integration tests that depend on local endpoints. Finally, keep an eye on the upcoming cf CLI releases, which will build on the same configuration foundation introduced in v5.

Tags: #miniflare#cloudflare#workers#devops
Originally published atCloudflare Developer Platform
Related Articles
Cloudflare

Pin exact npm (or Yarn/pnpm/Bun) version in Cloudflare Workers Builds

2 min read
Cloudflare

D1 undelete window narrowed to 7 days – adjust your recovery process

2 min read
Cloudflare

Flagship adds native support for nested objects and arrays in evaluation context

3 min read