Binding reference Bindings

Use Rate Limiting in a Worker

Rate Limiting bindings let Workers enforce fixed-window limits from inside application code.

Add the Rate Limiting config, call from worker code, and start with the local test path Devflare supports.

Start with the config, wire the binding into worker code, then use the support section to decide whether local tests or Cloudflare-backed tests fit.

Config key
Authoring shape
Best for: login throttles, per-user limits, and API guardrails that can use Cloudflare fixed windows

Add the binding to config

Add to , then use the generated env binding from Worker code.

Keep the first version close to the route or handler that needs it; move to a helper only after the shape is obvious.

Smallest Rate Limiting config

import { defineConfig } from 'devflare/config'

export default defineConfig({

name: 'limited-worker',

bindings: {

rateLimits: {

LOGIN_RATE_LIMIT: {

namespaceId: '1001',

simple: {

limit: 20,

period: 60

}

})

Use the binding from application code

After Devflare generates the worker env, import from and keep the first Rate Limiting path close to the route, handler, or service method that needs it.

Keep this first path small enough that the config, env binding, and user-visible behavior are easy to review together.

Use the limiter in a request path

import { env } from 'devflare/runtime'

export async function fetch(request: Request): Promise<Response> {

const key = request.headers.get('cf-connecting-ip') ?? 'local'

const outcome = await env.LOGIN_RATE_LIMIT.limit({ key })

if (!outcome.success) {

return new Response('slow down', { status: 429 })

}

return new Response('ok')

}

Local and Remote Support

Devflare can run useful Rate Limiting application behavior locally for ordinary development and tests. Cloudflare still owns production limits, quotas, billing, and deployed account behavior.

Offline-native: Miniflare and Devflare pure mocks can exercise application-level rate limit behavior. Start locally with or ; that lane should cover the normal Rate Limiting application flow without requiring a Cloudflare connection.

Use Cloudflare when the assertion depends on deployed limits, account state, lifecycle behavior, billing, or other production-only Rate Limiting details.

When this binding fits best

Use Rate Limiting when login throttles, per-user limits, and api guardrails that can use cloudflare fixed windows.
Keep binding names stable and uppercase in examples so generated Env declarations remain predictable.
Prefer Devflare native config while it covers the feature; use only for unsupported Wrangler-only fields.

Testing path

Start with or for config-backed local worker tests.
Use / for small unit tests that only need deterministic application behavior.
Use Cloudflare-backed tests when the assertion depends on hosted platform behavior, account state, limits, billing, or production routing.

Open the next page when you need it

Subpage

Rate Limiting internals

Internals

Check emitted Wrangler , preview behavior, and Cloudflare-specific details.

Subpage

Testing Rate Limiting

Testing

Pick the or path first, then move to remote checks only when the test needs them.

Subpage

Rate Limiting example

Example

Copy a fuller application path when the quick example is too small.