Hi! There is limit of maximum static assets files inside the new product « Workers with assets » ?

GGuillaumeLakano Hi! There is limit of maximum static assets files inside the new product « Worke...

C

Chaika•10/15/24, 7:33 PM

Same as Pages workers-and-pages-discussions

C

Constantin•10/15/24, 8:06 PM

@Chaika it looks that at some point (in the proxy worker) i have to fetch the Astro page ..

C

Constantin•10/15/24, 8:08 PM

or a better solution would be to get rid of pages, and use astro as a worker .. but this comes with it's own limitations

C

Constantin•10/15/24, 8:10 PM

I didn't think that implementing custom domains could be so difficult

C

Constantin•10/15/24, 8:11 PM

M

Mozzy•10/15/24, 8:15 PM

Has anyone tried a canvas package on the latest Workers compatibility? node-canvas, napi-rs/canvas, etc. I assume it doesn't work

On a relevant note, is there any reality in which one of those packages would/could ever work directly on Workers without needing any external service or browsing?

Original message was deleted

H

Hello, I’m Allie!•10/15/24, 9:44 PM

Sort of? At the moment, if a route has an asset that matches the path exactly, then that asset will be served. One way to get around this is to put the assets in a different directory(

/cdn-cgi/assets/index.html

/cdn-cgi/assets/index.html

/cdn-cgi/assets/index.html

/cdn-cgi/assets/index.html maybe)

WWalshy You can set a lower timeout with AbortSignal - <https://developer.mozilla.org/en...

C

Codex•10/15/24, 9:53 PM

This was a legendary callout, thank you for this, I completely forgot signals were a thing

F

Felix Chen•10/15/24, 10:26 PM

Hi guys I just wrote a simple worker to use workers ai with ollama-style API

F

Felix Chen•10/15/24, 10:26 PM

And I wonder if there is a way to add rate limiter without durable objects or kv storage

F

Felix Chen•10/15/24, 10:26 PM

As there is no authentication in ollama API

F

Felix Chen•10/15/24, 10:26 PM

https://github.com/ailelix/cf-workers-ai-ollama-api

GitHub

GitHub - ailelix/cf-workers-ai-ollama-api: Use Cloudflare Workers A...

Use Cloudflare Workers AI with Ollama-Style API. Contribute to ailelix/cf-workers-ai-ollama-api development by creating an account on GitHub.

A

Akash•10/16/24, 5:58 AM

Is there any plan to support permissions for service bindings? I would like to have two workers where one is having write permission on a kv namespace but other is having only read permission.

A

Alexander Hupfer•10/16/24, 7:18 AM

what's going on here? Are workers not good anymore?

C

Constantin•10/16/24, 8:01 AM

hey, i'm following this guide https://developers.cloudflare.com/workers/frameworks/framework-guides/astro/ to create an Astro Worker .. all good, however, when i try to create a wrangler.toml file, i'm not sure what the path for the main key should be. any ideeas?

C

Constantin•10/16/24, 8:53 AM

nope, the ci pipline is failing with this error

C

Constantin•10/16/24, 8:53 AM

this is how the action looks

C

Constantin•10/16/24, 9:23 AM

oh, i see .. i wrongly thought that this deploy in package json is the same in action

C

Constantin•10/16/24, 9:24 AM

but i think there are two different commands (one for the project, another for wrangler)

Original message was deleted

A

Alexander Hupfer•10/16/24, 12:50 PM

Which package?

N

nikita•10/16/24, 2:57 PM

Hi all, I need your help with the Worker setup. We have a Worker with the wildcard for the hostname in the routes in wrangler.toml:

routes = [ 
    { pattern="*/cdn/*", zone_id="xxxxxxId" }
]

routes = [ 
    { pattern="*/cdn/*", zone_id="xxxxxxId" }
]

routes = [ 
    { pattern="*/cdn/*", zone_id="xxxxxxId" }
]

routes = [ 
    { pattern="*/cdn/*", zone_id="xxxxxxId" }
]

The reason we have this setup is that we wanted the Worker to trigger for our clients’ custom domains dynamically connected via Cloudflare for SaaS. e.g.

example.org is our domain
client1.org CNAME cname.example.org -> client1 domain connected to ours
client2.org CNAME cname.example.org -> client2 domain connected to ours

example.org is our domain
client1.org CNAME cname.example.org -> client1 domain connected to ours
client2.org CNAME cname.example.org -> client2 domain connected to ours

example.org is our domain
client1.org CNAME cname.example.org -> client1 domain connected to ours
client2.org CNAME cname.example.org -> client2 domain connected to ours

example.org is our domain
client1.org CNAME cname.example.org -> client1 domain connected to ours
client2.org CNAME cname.example.org -> client2 domain connected to ours

The same worker used to trigger for requests to

example.org

example.org

example.org

example.org,

client1.org

client1.org

client1.org

client1.org &

client2.org

client2.org

client2.org

client2.org. Recently, when publishing the Worker, we started to experience the error :

Route pattern must include zone name: example.org [code: 10022]

Route pattern must include zone name: example.org [code: 10022]

Route pattern must include zone name: example.org [code: 10022]

Route pattern must include zone name: example.org [code: 10022]

It looks like something has changed recently. What is the recommended Wrangler routes setup for the worker to trigger for every dynamically connected custom domain in Cloudflare?

J

Jadugar_Jaggu•10/16/24, 3:00 PM

In Cloudflare Workers, the uploaded script is undergoing modifications by internal algorithms during the deployment process via Wrangler. Specifically, the original function in the script, found at this GitHub link: https://github.com/subhendukundu/worker-auth-providers/blob/d979f59fb1eb9129de7dcb8e6209cf2c120fc7c9/dist/providers/google/redirect.js#L3, has been altered, leading to unexpected behavior in production. Locally, everything functions as intended.

The issue arises from a discrepancy between the original code and the uploaded version. The package author suggests using the redirectTo parameter instead of redirectUrl. I am correctly passing the redirect_uri value through the redirectTo variable, but in the uploaded worker script, redirectTo is missing from the function. This bug is significantly impacting user sign-in and sign-up processes, as this package is responsible for handling the Google sign-in flow.

I would suggest to look into it

GitHub

worker-auth-providers/dist/providers/google/redirect.js at d979f59f...

worker-auth-providers is an open-source providers to make authentication easy with workers. Very lightweight script which doesn't need a lot of dependencies. Plug it with any framework or t...

JJadugar_Jaggu In Cloudflare Workers, the uploaded script is undergoing modifications by intern...

J

Jadugar_Jaggu•10/16/24, 3:01 PM

This is an serious issue. Cloudflare team should look into this matter

Nnikita Hi all, I need your help with the Worker setup. We have a Worker with the wildc...

C

Chaika•10/16/24, 3:01 PM

Route pattern must include zone name: example.org [code: 10022]

afaik that error means you don't have CF For SaaS enabled on the zone you're trying to add the route on

JJadugar_Jaggu In Cloudflare Workers, the uploaded script is undergoing modifications by intern...

C

Chaika•10/16/24, 3:04 PM

Wrangler just uses esbuild, shouldn't do anything that crazy. Your code you showed is equal to the older version of the package: https://github.com/subhendukundu/worker-auth-providers/blob/7548cda3470072a9a276fd32637b079140728172/dist/providers/google/redirect.js so probably just not updating properly/looking at code from an old push or something else

CChaika Wrangler just uses esbuild, shouldn't do anything that crazy. Your code you show...

J

Jadugar_Jaggu•10/16/24, 3:06 PM

You can see here in VS CODE, I have the latest one

J

Jadugar_Jaggu•10/16/24, 3:09 PM

and one more thing this issue arises recently, may be this month, previously it was working fine. Thats why I checked the uploaded code in cloudflare to find some traces

J

Jadugar_Jaggu•10/16/24, 3:17 PM

Never Mind, its fixed now, after removing and adding the pakage again

S

Shados•10/16/24, 4:19 PM

Hi everyone. I've searched on the discord and the docs, and there's discussion around worker size limit, but couldn't figure out exactly what "counts" or how to calculate the exact size of my app.

We are on an enterprise plan, and I know right now we're nowhere close to the limit with our prod app, but I want to plan for the future. I know its gzipped size, 10mb limit, but what "counts"? Is it everything thats uploaded to the worker? Do the new static asset support count or not? I upload sourcemaps with the code, do the sourcemaps count?

Any patterns people use to reduce size that I should know from day 1? (eg: obviously large static assets should be hosted outside of the Worker. Anything else in the captain obvious category)?

SShados Hi everyone. I've searched on the discord and the docs, and there's discussion a...

C

Chaika•10/16/24, 4:21 PM

gzipped size is what matters. Static uploads are separate. Source maps are seperate too and have a pretty strict size limit of their own (I think 1mb or something? I can't find at a glance in docs)

S

Shados•10/16/24, 4:21 PM

Is there a way in Wrangler or the dashboard to see the size of my worker as it matters to that limit?

C

Chaika•10/16/24, 4:21 PM

When you upload a worker in a recentish wrangler version it'll throw out your gzipped size

C

Chaika•10/16/24, 4:23 PM

Total Upload: 10.17 KiB / gzip: 2.57 KiB

S

Shados•10/16/24, 4:23 PM

Oh yeah, lookie at that!

S

Shados•10/16/24, 4:23 PM

Excellent, thank you, once again.

C

Constantin•10/16/24, 4:35 PM

howdy, does CF API can be binded? i mean is it possible to interact with custom domains api in a RPC way?

CChaika > Route pattern must include zone name: example.org [code: 10022] afaik that err...

N

nikita•10/16/24, 4:37 PM

Thank you, you are right. It looks like it got switched off at some point when our billing failed.

CConstantin howdy, does CF API can be binded? i mean is it possible to interact with custom ...

C

Chaika•10/16/24, 4:39 PM

not currently, have to go through the normal rest api

1

123generic•10/16/24, 11:05 PM

Hi all, is there a way to provide "deletion protection" to a worker? One of our developers accidentally deleted a worker we were using in production. It's easy to redeploy, but I'd prefer a better solution.

C

Constantin•10/17/24, 12:43 AM

hey there how can i pass github env vars to a worker/astro?

when using astro as a Page (not a worker) i can use the locals.runtime.env.CF_PAGES_BRANCH

C

Constantin•10/17/24, 12:43 AM

however, with workers, there's a github pipeline in place

C

Constantin•10/17/24, 12:45 AM

i added them in the global scope.. still they are not available not on locals.runtime.env or import.meta.env

W

Walshy•10/17/24, 12:48 AM

You'd need to inject them into the env in some way

W

Walshy•10/17/24, 12:48 AM

You could use --var or replace contents in wrangler.toml

W

Walshy•10/17/24, 12:49 AM

E.g

wrangler deploy --var GH_SHA=$GITHUB_SHA

wrangler deploy --var GH_SHA=$GITHUB_SHA

wrangler deploy --var GH_SHA=$GITHUB_SHA

wrangler deploy --var GH_SHA=$GITHUB_SHA

C

Constantin•10/17/24, 1:03 AM

ty @Walshy | Out of office

C

Constantin•10/17/24, 2:21 AM

does any of you manage to render assets in astro in a different way than setting assets = { directory = "./dist" } in wrangler.toml .. by setting in wrangler you can't use placement smart, plus some other limitations.

A

Adi•10/17/24, 7:00 AM

So I upgraded to the latest version of wrangler and deployed a website using

wrangler deploy

wrangler deploy

  Total Upload: 3324.79 KiB / gzip: 1022.32 KiB
  Worker Startup Time: 235 ms
  Your worker has access to the following bindings:
  - KV Namespaces:
    - CACHIFIED_CACHE: 191f201005724b038b6facd2ae37e1d9
  - Services:
    - PUBLIC_DATA_SERVICE: 🔴 naamdeo-courses-api#PublicDataService
    - AUTHENTICATED_USER_SERVICE: 🔴 naamdeo-courses-api#AuthenticatedUserService
    - RESTRICTED_SERVICE: 🔴 naamdeo-courses-api#RestrictedService

  Total Upload: 3324.79 KiB / gzip: 1022.32 KiB
  Worker Startup Time: 235 ms
  Your worker has access to the following bindings:
  - KV Namespaces:
    - CACHIFIED_CACHE: 191f201005724b038b6facd2ae37e1d9
  - Services:
    - PUBLIC_DATA_SERVICE: 🔴 naamdeo-courses-api#PublicDataService
    - AUTHENTICATED_USER_SERVICE: 🔴 naamdeo-courses-api#AuthenticatedUserService
    - RESTRICTED_SERVICE: 🔴 naamdeo-courses-api#RestrictedService

  Total Upload: 3324.79 KiB / gzip: 1022.32 KiB
  Worker Startup Time: 235 ms
  Your worker has access to the following bindings:
  - KV Namespaces:
    - CACHIFIED_CACHE: 191f201005724b038b6facd2ae37e1d9
  - Services:
    - PUBLIC_DATA_SERVICE: 🔴 naamdeo-courses-api#PublicDataService
    - AUTHENTICATED_USER_SERVICE: 🔴 naamdeo-courses-api#AuthenticatedUserService
    - RESTRICTED_SERVICE: 🔴 naamdeo-courses-api#RestrictedService

  Total Upload: 3324.79 KiB / gzip: 1022.32 KiB
  Worker Startup Time: 235 ms
  Your worker has access to the following bindings:
  - KV Namespaces:
    - CACHIFIED_CACHE: 191f201005724b038b6facd2ae37e1d9
  - Services:
    - PUBLIC_DATA_SERVICE: 🔴 naamdeo-courses-api#PublicDataService
    - AUTHENTICATED_USER_SERVICE: 🔴 naamdeo-courses-api#AuthenticatedUserService
    - RESTRICTED_SERVICE: 🔴 naamdeo-courses-api#RestrictedService

This must be a recent change, can I just say, the red dot is kind of scary

I thought something was broken for a second, but I think it's just a choice someone made haha.

E

Elliot Hesp•10/17/24, 8:13 AM

If I have a worker which proxies a websocket request, am I charged for messages to the proxied endpoint or just the initial request

BBrett Willis Needing some help, is there is no mechanism for handling the event that a client...

B

Brett Willis•10/17/24, 8:50 AM

[Feature request] The

Request.signal

Request.signal

Request.signal

Request.signal API (https://developer.mozilla.org/en-US/docs/Web/API/Request/signal) would be a convenient API to utilise for signalling when the client has disconnected. Currently we have no what of detecting when the request has been cancelled. Particularly important for SSE/streaming scenarios.
Another potential API (new) could be something like

ctx.addEventListener('end', () => {})

ctx.addEventListener('end', () => {})

ctx.addEventListener('end', () => {})

ctx.addEventListener('end', () => {}).