From dc442c36036c0cf5142c087625766650d1e7ec41 Mon Sep 17 00:00:00 2001 From: MichielKikkert Date: Mon, 3 Feb 2025 20:43:37 +0100 Subject: [PATCH 1/2] Update index.mdx Changed Limitation bullet 3. CF/Wrangler no longer seems to error but just warn if you have a worker with an asset binding and deploy on a route with a path component. --- src/content/docs/workers/static-assets/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/workers/static-assets/index.mdx b/src/content/docs/workers/static-assets/index.mdx index 42fb9d2f6e519ee..5b1a7fe3dbe3eb7 100644 --- a/src/content/docs/workers/static-assets/index.mdx +++ b/src/content/docs/workers/static-assets/index.mdx @@ -79,7 +79,7 @@ The following limitations apply for Workers with static assets: - There is a 20,000 file count limit per [Worker version](/workers/configuration/versions-and-deployments/), and a 25 MiB individual file size limit. This matches the [limits in Cloudflare Pages](/pages/platform/limits/) today. - In local development, you cannot make [Service Binding RPC calls](/workers/runtime-apis/bindings/service-bindings/rpc/) to a Worker with static assets. This is a temporary limitation, we are working to remove it. -- Workers with assets cannot run on a [route or domain](/workers/configuration/routing/) with a path component. For example, `example.com/*` is an acceptable route, but `example.com/foo/*` is not. Wrangler and the Cloudflare dashboard will throw an error when you try and add a route with a path component. +- Workers with assets will warn if ran on a [route or domain](/workers/configuration/routing/) with a path component. For example, `example.com/*` is an acceptable route, but `example.com/foo/*` will give a warning. Wrangler and the Cloudflare dashboard will show this warning when you try and add a route with a path component. :::note From a3d775b09024fd65c4f365248a2455feea77b7e8 Mon Sep 17 00:00:00 2001 From: MichielKikkert Date: Mon, 3 Feb 2025 21:14:41 +0100 Subject: [PATCH 2/2] Update src/content/docs/workers/static-assets/index.mdx Applied suggestion Co-authored-by: Greg Brimble --- src/content/docs/workers/static-assets/index.mdx | 1 - 1 file changed, 1 deletion(-) diff --git a/src/content/docs/workers/static-assets/index.mdx b/src/content/docs/workers/static-assets/index.mdx index 5b1a7fe3dbe3eb7..7d767ead30c2b72 100644 --- a/src/content/docs/workers/static-assets/index.mdx +++ b/src/content/docs/workers/static-assets/index.mdx @@ -79,7 +79,6 @@ The following limitations apply for Workers with static assets: - There is a 20,000 file count limit per [Worker version](/workers/configuration/versions-and-deployments/), and a 25 MiB individual file size limit. This matches the [limits in Cloudflare Pages](/pages/platform/limits/) today. - In local development, you cannot make [Service Binding RPC calls](/workers/runtime-apis/bindings/service-bindings/rpc/) to a Worker with static assets. This is a temporary limitation, we are working to remove it. -- Workers with assets will warn if ran on a [route or domain](/workers/configuration/routing/) with a path component. For example, `example.com/*` is an acceptable route, but `example.com/foo/*` will give a warning. Wrangler and the Cloudflare dashboard will show this warning when you try and add a route with a path component. :::note