Ship Globally from Your Terminal: Cloudflare Workers CLI & Simulator

You've probably heard about Cloudflare Workers — that edge computing platform that lets you run JavaScript at the speed of light, literally at the edge. But if you've ever tried to set up the local development workflow, you know it can get a bit tangled. Wrangler? Miniflare? wrangler2? It’s a lot.

That’s where the workers-sdk repo comes in. It’s the monorepo that holds the Cloudflare Workers CLI (wrangler) and the Workers Simulator (miniflare), all in one place. Think of it as your one-stop shop for building, testing, and deploying serverless functions globally — without leaving your terminal.

What It Does

The workers-sdk repo is the official source for two core tools:

• wrangler – The CLI that handles everything from local development to production deployment of your Workers, Pages, R2 buckets, and more.
• miniflare – A full-featured local simulator that mimics the Cloudflare Workers runtime. It means you can run your Workers code locally, test against KV, Durable Objects, Queues, and even R2 before you push to the edge.

Together, they give you a tight loop: write code, test locally with miniflare, then deploy globally with wrangler — all from the command line.

Why It’s Cool

Let’s be real: deploying to the edge is neat, but debugging at the edge is a nightmare. The killer feature here is the local simulation. Miniflare isn’t just a mock — it’s a pretty faithful emulation of the actual Workers runtime. You can run your entire Worker, including Durable Objects, Queues, and scheduled events, right on your laptop. No need to cloud-commit every time you want to see if your KV lookups work.

Also, the CLI is surprisingly ergonomic. wrangler init scaffolds a project. wrangler dev starts a local server. wrangler publish sends it to the edge. It’s clean, predictable, and handles a lot of the config boilerplate (like API tokens and zones) behind the scenes. If you've used other serverless tools (like the Serverless Framework or AWS SAM), you’ll feel right at home — but with way less YAML.

One more thing: because this is a monorepo, you get updates for both tools in a single npm install -g wrangler. No more fighting version mismatches between wrangler and miniflare.

How to Try It

Getting started is a few commands away:

1. Install the CLI (if you haven't already):

   npm install -g wrangler
   

2. Create a new Worker project:

   wrangler init my-worker
   cd my-worker
   

3. Run it locally with the simulator:

   wrangler dev
   

   This will spin up a local server on http://localhost:8787. Any changes you make to your Worker code are hot-reloaded instantly. It even simulates KV and Durable Objects if you've set them up in wrangler.toml.

4. Deploy to the edge (after you log in):

   wrangler login
   wrangler publish
   

That’s it. No docker containers, no cloud accounts needed for local testing. Just code, test, ship.

Final Thoughts

I’ve seen a lot of serverless tools come and go. Most either make you jump through hoops to test locally, or they abstract away so much that you lose control. The Cloudflare Workers CLI + Simulator actually reduces friction without hiding the details. You get the full power of the edge platform with a local dev experience that doesn’t feel like a compromise.

If you’re building anything that benefits from low-latency global execution (think APIs, redirects, A/B testing, or even full-blown SSR), this stack is worth a weekend play. And with the workers-sdk repo, you’re getting the latest and greatest in one tidy package.

Go build something at the edge — from your localhost.

Follow @githubprojects for more developer-friendly tools and project breakdowns.