splitting would work if each execution only needed some or none of the split workers, wouldnt be ver

E

ErisaOP•9/9/24, 1:35 PM

just generally the only advice in this case is to make the worker smaller, how to do that will depend on the exact use-case

EErisa splitting would work if each execution only needed some or none of the split wor...

P

Ping for toast•9/9/24, 1:36 PM

This would be the case. OG image generation is just needed when another website requests it

E

ErisaOP•9/9/24, 1:37 PM

then yeah try splitting OG image gen into its own worker

P

Ping for toast•9/9/24, 1:37 PM

I'll try that ig

E

ErisaOP•9/9/24, 1:37 PM

test whether that helps and iterate accordingly

E

ErisaOP•9/9/24, 1:37 PM

you should connect to the split worker over a service binding to remove any network latency from the worker-to-worker fetch

EErisa you should connect to the split worker over a service binding to remove any netw...

P

Ping for toast•9/9/24, 1:38 PM

Could I also do workers routes? If I had one worker pointing to

/api/*

/api/*

and another one pointing to

/api/og/*

/api/og/*

/api/og/*

/api/og/*

PPing for toast og is 27% of the bundle

P

Ping for toast•9/9/24, 1:39 PM

One bundle size fantasy (unrelated to OG generation) I've had for years is macros in bundlers

E

ErisaOP•9/9/24, 1:39 PM

oh rite you said the website is requesting the worker, in that case yeah you can do routes like that

E

ErisaOP•9/9/24, 1:39 PM

its if you wanted your main worker to act on the response that youd have to use service binding since same-zone fetch doesnt work

P

Ping for toast•9/9/24, 1:40 PM

ye

E

ErisaOP•9/9/24, 1:40 PM

but if its just a different api endpoint by all means use routes like that

P

Paolo•9/9/24, 4:25 PM

does a worker created with the dashaboard support ES modules? Or can that be done only via wrangler? I see the wrangler.toml file at creation but I can't edit it. Can it be done after creation?

M

Mike D.•9/9/24, 6:24 PM

https://github.com/cloudflare/workers-sdk/issues/6657 having issue with typescript

GitHub

🐛 BUG: Uncaught SyntaxError: Unexpected token '<' for embedded type...

Which Cloudflare product(s) does this pertain to? Wrangler What version(s) of the tool(s) are you using? 3.75.0 wrangler What version of Node are you using? v22 pre What operating system and versio...

M

Mike D.•9/9/24, 6:26 PM

https://github.com/meta-introspector/mina-snarky-o1js-zkapp-introspector/actions/runs/10778636802/job/29890420745#step:4:61 this one in github actions fails because it cannot find the source

GitHub

moving to ui dir · meta-introspector/mina-snarky-o1js-zkapp-introsp...

zkIntrospector: A Self-Aware zkApp Framework for Gödel Number Reflection - moving to ui dir · meta-introspector/mina-snarky-o1js-zkapp-introspector@a6f3f9a

M

Mike D.•9/9/24, 7:05 PM

i will rename it if it helps

M

Mike D.•9/9/24, 7:25 PM

that did not help, also o1js needs threads so i might have to go to another solutions

G

garb•9/10/24, 2:25 AM

Hey guys, is anyone else's audit throwing a high severity error with cloudflare/vitest-pool-workers & wrangler.

G

garb•9/10/24, 2:26 AM

# npm audit report

path-to-regexp  0.2.0 - 7.2.0
Severity: high
path-to-regexp outputs backtracking regular expressions - https://github.com/advisories/GHSA-9wv6-86v2-598j
No fix available
node_modules/path-to-regexp
  wrangler  <=0.0.0-kickoff-demo || >=0.0.7
  Depends on vulnerable versions of path-to-regexp
  node_modules/wrangler
    @cloudflare/vitest-pool-workers  *
    Depends on vulnerable versions of wrangler
    node_modules/@cloudflare/vitest-pool-workers

3 high severity vulnerabilities

# npm audit report

path-to-regexp  0.2.0 - 7.2.0
Severity: high
path-to-regexp outputs backtracking regular expressions - https://github.com/advisories/GHSA-9wv6-86v2-598j
No fix available
node_modules/path-to-regexp
  wrangler  <=0.0.0-kickoff-demo || >=0.0.7
  Depends on vulnerable versions of path-to-regexp
  node_modules/wrangler
    @cloudflare/vitest-pool-workers  *
    Depends on vulnerable versions of wrangler
    node_modules/@cloudflare/vitest-pool-workers

3 high severity vulnerabilities

# npm audit report

path-to-regexp  0.2.0 - 7.2.0
Severity: high
path-to-regexp outputs backtracking regular expressions - https://github.com/advisories/GHSA-9wv6-86v2-598j
No fix available
node_modules/path-to-regexp
  wrangler  <=0.0.0-kickoff-demo || >=0.0.7
  Depends on vulnerable versions of path-to-regexp
  node_modules/wrangler
    @cloudflare/vitest-pool-workers  *
    Depends on vulnerable versions of wrangler
    node_modules/@cloudflare/vitest-pool-workers

3 high severity vulnerabilities

# npm audit report

path-to-regexp  0.2.0 - 7.2.0
Severity: high
path-to-regexp outputs backtracking regular expressions - https://github.com/advisories/GHSA-9wv6-86v2-598j
No fix available
node_modules/path-to-regexp
  wrangler  <=0.0.0-kickoff-demo || >=0.0.7
  Depends on vulnerable versions of path-to-regexp
  node_modules/wrangler
    @cloudflare/vitest-pool-workers  *
    Depends on vulnerable versions of wrangler
    node_modules/@cloudflare/vitest-pool-workers

3 high severity vulnerabilities

G

garb•9/10/24, 2:27 AM

Wrangler is on version 3.75.0.

S

sathoro•9/10/24, 4:36 AM

anyone know if it is possible to use fetch with a proxy now? I tried

https-proxy-agent

https-proxy-agent

https-proxy-agent

https-proxy-agent but getting

TypeError: Cannot convert object to primitive value

TypeError: Cannot convert object to primitive value

TypeError: Cannot convert object to primitive value

TypeError: Cannot convert object to primitive value when calling

new HttpsProxyAgent(proxyUrl)

new HttpsProxyAgent(proxyUrl)

new HttpsProxyAgent(proxyUrl)

new HttpsProxyAgent(proxyUrl)

S

sathoro•9/10/24, 4:41 AM

another attempt with a different package, no error but this just ignores the proxy

import { createFetch } from "node-fetch-native/proxy";

const fetch = createFetch({ url: proxyUrl });
await fetch(targetUrl);

import { createFetch } from "node-fetch-native/proxy";

const fetch = createFetch({ url: proxyUrl });
await fetch(targetUrl);

import { createFetch } from "node-fetch-native/proxy";

const fetch = createFetch({ url: proxyUrl });
await fetch(targetUrl);

import { createFetch } from "node-fetch-native/proxy";

const fetch = createFetch({ url: proxyUrl });
await fetch(targetUrl);

S

sathoro•9/10/24, 4:43 AM

I'm guessing whatever it does behind-the-scenes just gets pollyfilled back to CF's regular fetch function so it won't be possible

J

Jess•9/10/24, 4:53 AM

Hello my name is jess and I would like to know if there is any advise for captcha error when trying to log in using citrix?

G

garb•9/10/24, 5:13 AM

I submitted a forum in #workers-help

G

garb•9/10/24, 5:13 AM

workers-and-pages-helpUpdate path-to-regexp package to 8.0.0 @veikkoeeva

G

garb•9/10/24, 5:13 AM

There is a fix contained but still waiting for something official from the wrangler team

G

garb•9/10/24, 5:30 AM

I am strictly on workers, path-to-regexp seems to be only ran via wrangler/templates/pages-template-plugin.ts & pages-template-index.ts

G

garb•9/10/24, 5:30 AM

G

garb•9/10/24, 5:31 AM

I don't recommend using my fix for a production environment.

G

garb•9/10/24, 5:31 AM

But for those with pipelines that build and test for a staging site haha

N

Noil•9/10/24, 10:51 AM

When running my worker on --remote I am getting a [WARNING] worker failed to prewarm: Bad Gateway.

What could possibly be the cause of this?

A

Andre•9/10/24, 12:01 PM

Hi everyone,
I'm on a worker pro plan and I'm getting rate limited (around 2k requests per minute it seems).
It's not clear to me what are the limit exactly reading the documentation https://developers.cloudflare.com/workers/platform/limits/
Can this limit be increased by reaching out the support via Discord or can this only be done through a ticket from the Dashboard?

M

mo246•9/10/24, 2:20 PM

Hi, was curious as to if anyone here is using workers with AI in a chrome extension. I wanted to use a worker as a proxy to call the Anthropic/OpenAI API to feed the results back to my extension. But I’m concerned about the exposure of the workers.dev domain url in the code. Anyone can access chrome extension if they know what they’re doing and obtain the endpoint url and probably make a million requests to it.

Is this something I should be concerned about or am I just overthinking here.

H

Hammer•9/10/24, 4:52 PM

whats the best web stack for cloudflare workers?

H

Hammer•9/10/24, 4:52 PM

hono?

Vveikkoeeva https://developers.cloudflare.com/workers/configuration/sites/start-from-worker/...

A

Ashley•9/10/24, 6:37 PM

This is a really old page, as it says - you should use Cloudflare Pages now, it’s probably just there for anyone still using Worker Sites

Vveikkoeeva Are Worker Sites the same or a different thing as Cloudflare Worker that fetches...

W

Wallacy•9/10/24, 11:19 PM

Thats is Worker Sites.

D

Dawson•9/11/24, 12:43 AM

Can I have a cf worker that redirects subdomain

abc.foo.bar

abc.foo.bar

abc.foo.bar

abc.foo.bar to

ip:port

ip:port

ip:port

ip:port dynamically from a db?

D

Dawson•9/11/24, 12:44 AM

I want to dynamically create minecraft servers and have a sub domain generated alongside them pretty much

D

Dawson•9/11/24, 12:44 AM

Just curious if I can do this with cloudflare workers

W

Walshy•9/11/24, 12:44 AM

so, yes

splitting would work if each execution only needed some or none of the split workers, wouldnt be ver

Similar Threads

Similar Threads

Similar Threads