Cloudflare / Cloudflare

Cloudflare Pages Functions catchall routes return 1101 due to path-to-regexp v6/v8 syntax mismatch

Fix Cloudflare Pages Functions returning 1101 error on all URLs when using [[name]].ts catchall route files (wrangler 4.77+) Includes evidence for Cloudflare troubleshooting demand.

Source-backed Last updated May 22, 2026 1 source Needs local verification

Category: Cloudflare
Error signature: TypeError: Missing parameter name at index 11: /:catchall* → Cloudflare Error 1101 Worker threw exception
Quick fix: Compare the failing environment with a known working setup, then change one configuration value at a time.
Updated: May 22, 2026
Verification status: Source-backed
Evidence: 1 public source URL

Before you change production

This page includes public source URLs in the imported troubleshooting record. Compare those references with your version and environment before applying changes.

Reproduce the smallest failing action and save non-secret logs before changing configuration.
Check versions for Cloudflare, related SDKs, package managers, CI runners, and hosting providers.
Change one setting or dependency at a time, then rerun the same failing command or request.
Avoid destructive commands, credential rotation, billing changes, or security relaxations without a rollback plan.

What this error means

TypeError: Missing parameter name at index 11: /:catchall* → Cloudflare Error 1101 Worker threw exception is a Cloudflare failure pattern reported for developers trying to fix cloudflare pages functions returning 1101 error on all urls when using [[name]].ts catchall route files (wrangler 4.77+). Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

GitHub issue #13643 on cloudflare/workers-sdk is a deterministic, reproducible bug: wrangler emits path-to-regexp v6 syntax (/\:name*) in the routes manifest, but bundles v8 which rejects it. Affects ALL Pages projects using documented catchall filename convention. Clear error signature, specific workaround exists (rename to _middleware.ts), and cross-verified across two wrangler versions (4.77.0, 4.84.1). Very high commercial value — breaks live deployments.

Common causes

GitHub issue #13643 on cloudflare/workers-sdk is a deterministic, reproducible bug: wrangler emits path-to-regexp v6 syntax (/\:name*) in the routes manifest, but bundles v8 which rejects it. Affects ALL Pages projects using documented catchall filename convention. Clear error signature, specific workaround exists (rename to _middleware.ts), and cross-verified across two wrangler versions (4.77.0, 4.84.1). Very high commercial value — breaks live deployments.

Quick fixes

Confirm the exact error signature matches TypeError: Missing parameter name at index 11: /:catchall* → Cloudflare Error 1101 Worker threw exception.
Check the Cloudflare account, local tool state, and provider configuration involved in the failing workflow.
Compare the failing environment with a known working setup, then change one configuration value at a time.

Platform/tool-specific checks

Verify the command, editor, extension, or API client that produced the error.
Compare local settings with CI, deployment, or editor-level settings when the error appears in only one environment.
Avoid deleting credentials, local model data, or project settings until the failing scope is clear.

Step-by-step troubleshooting

Capture the exact error message and the command, editor action, or request that triggered it.
Check whether the failure is account/auth, quota/rate, model/provider, local runtime, or deployment configuration.
Review the source evidence below and compare it with your environment.
Apply one change at a time and rerun the smallest failing action.
Keep the working fix documented for the team or deployment environment.

How to prevent it

Keep provider/tool configuration documented.
Record non-secret diagnostics such as tool version, provider name, model name, and command path.
Add a lightweight check before CI or production workflows depend on the tool.

Diagnostic flow for this page

Match TypeError: Missing parameter name at index 11: /:catchall* → Cloudflare Error 1101 Worker threw exception exactly before applying the quick fix.
Compare the failing environment with Cloudflare versions, account scope, provider settings, and deployment context.
Check the listed common causes in order, starting with the cause that best matches your logs.
Use the evidence status below to decide whether to confirm against public sources or official documentation.
Apply one reversible change, rerun the smallest failing action, and keep rollback notes.

FAQ

What does TypeError: Missing parameter name at index 11: /:catchall* → Cloudflare Error 1101 Worker threw exception mean in Cloudflare?

TypeError: Missing parameter name at index 11: /:catchall* → Cloudflare Error 1101 Worker threw exception indicates the workflow described by "Cloudflare Pages Functions catchall routes return 1101 due to path-to-regexp v6/v8 syntax mismatch" failed in a Cloudflare context. Start by confirming the exact signature and the component that emitted it.

What should I check first for TypeError: Missing parameter name at index 11: /:catchall* → Cloudflare Error 1101 Worker threw exception?

Check whether this cause matches your environment: GitHub issue #13643 on cloudflare/workers-sdk is a deterministic, reproducible bug: wrangler emits path-to-regexp v6 syntax (/\:name*) in the routes manifest, but bundles v8 which rejects it. Affects ALL Pages projects using documented catchall filename convention. Clear error signature, specific workaround exists (rename to _middleware.ts), and cross-verified across two wrangler versions (4.77.0, 4.84.1). Very high commercial value — breaks live deployments.

Is the TypeError: Missing parameter name at index 11: /:catchall* → Cloudflare Error 1101 Worker threw exception guidance source-backed?

The "Cloudflare Pages Functions catchall routes return 1101 due to path-to-regexp v6/v8 syntax mismatch" page is labeled source-backed. It has 1 public source URL from github.com, so use that evidence status when deciding how much additional verification you need.

When should I avoid the quick fix for TypeError: Missing parameter name at index 11: /:catchall* → Cloudflare Error 1101 Worker threw exception?

For "Cloudflare Pages Functions catchall routes return 1101 due to path-to-regexp v6/v8 syntax mismatch", avoid applying "Compare the failing environment with a known working setup, then change one configuration value at a time." when the error text differs, the affected version or provider is different, or the change would touch credentials, billing, DNS, production deploy settings, or irreversible data.

What should I collect before debugging TypeError: Missing parameter name at index 11: /:catchall* → Cloudflare Error 1101 Worker threw exception?

For "Cloudflare Pages Functions catchall routes return 1101 due to path-to-regexp v6/v8 syntax mismatch", collect the failing Cloudflare command or request, non-secret configuration, versions, timestamps, request IDs when available, and the smallest reproduction that still triggers the signature.