If i create a worker within the functions directory, will pages functions pick it up?

RRicky U If i create a worker within the functions directory, will pages functions pick i...

C

Cоle•4/10/25, 5:26 AM

not within

functions/

functions/

functions/

functions/ but https://developers.cloudflare.com/workers/static-assets/migrate-from-pages/#pages-functions-with-an-advanced-mode-_workerjs-file

3

39dylan•4/10/25, 5:55 AM

i have a static site that is too large for pages/workers (20k file limit) can i use cloudflare snippets + R2 storage to replicate this stack? it is simply a static site thats built on my local machine then uploaded old school way

L

LordSilver•4/10/25, 6:15 AM

just noticed playwright is now almost tripled puppeteer in just a year on npm. hopefully it becomes GA soon.

CChaika I tried the browser rendering rest api, fetching cloudflare.com/cdn-cgi/trace an...

L

LordSilver•4/10/25, 6:16 AM

makes sense. i wish we could get also the response headers alongside the html with the

/content

/content

/content

/content endpoint. :/

M

Mitya•4/10/25, 10:57 AM

Has anyone noticed that certain

console.log()

console.log()

console.log()

console.log() calls don't show up when working locally (in my case, with the

--remote

--remote

flag?) This happens all the time for me - and it's 100% not because the line of code doesn't run. Sometimes if I restart the worker it then fixes itself and logs show. Seemingly I can also fix it by just modifying an arbitrary line of code (or adding a space) so the worker gets freshly uploaded to the edge. Any one from CF know why this would happen? It's happened on multiple versions of Wrangler, too.

D

datacenterdude•4/10/25, 2:12 PM

Is there any documentation/BP on migrating a Pages site/repo to operate natively within a worker? So for example I have a worker running an API backend, but the swaggerUI is in a separate repo subfolder and Pages gets built from that. Can I just serve both from the worker efficiently? Just put /swagger in the same folder as the worker and wrangler deploy? I haven’t tried it yet but curious if other have and what stumbles they run into.

Ccardyet I'm a bit confused migrating from Pages to Workers for a NextJs project which ha...

W

Wouter J•4/10/25, 3:41 PM

Migrating from Pages to Workers, and away from @Cloudflare/workers-types but at this point i'm slowly starting to lose my mind.

D

datacenterdude•4/10/25, 5:57 PM

Moving my swagger page from Pages into Assets within the worker, and running into a new one I haven't seen where

wrangler deploy

wrangler deploy

is upset about the numbering of the arrays in the

wrangler.jsonc

wrangler.jsonc

wrangler.jsonc

wrangler.jsonc file. Feel like I'm missing something dumb...

But.... I've got the

"directory"

"directory"

"directory"

"directory" property defined.

{
  "name": "api",
  "main": "v1/index.ts",
  "compatibility_date": "2025-04-05",
  "d1_databases": [
    {
      "binding": "...",
      "database_name": "...",
      "database_id": "..."
    }
  ],
  "assets": [
    {
      "binding": "SWAGGER_JS",
      "directory": "./swagger",
      "pattern": "*.js"
    },
    {
      "binding": "SWAGGER_CSS",
      "directory": "./swagger",
      "pattern": "*.css"
    },
    {
      "binding": "SWAGGER_HTML",
      "directory": "./swagger",
      "pattern": "*.html"
    },
    {
      "binding": "SWAGGER_YAML",
      "directory": "./swagger",
      "pattern": "*.yaml"
    }
  ]
}

{
  "name": "api",
  "main": "v1/index.ts",
  "compatibility_date": "2025-04-05",
  "d1_databases": [
    {
      "binding": "...",
      "database_name": "...",
      "database_id": "..."
    }
  ],
  "assets": [
    {
      "binding": "SWAGGER_JS",
      "directory": "./swagger",
      "pattern": "*.js"
    },
    {
      "binding": "SWAGGER_CSS",
      "directory": "./swagger",
      "pattern": "*.css"
    },
    {
      "binding": "SWAGGER_HTML",
      "directory": "./swagger",
      "pattern": "*.html"
    },
    {
      "binding": "SWAGGER_YAML",
      "directory": "./swagger",
      "pattern": "*.yaml"
    }
  ]
}

{
  "name": "api",
  "main": "v1/index.ts",
  "compatibility_date": "2025-04-05",
  "d1_databases": [
    {
      "binding": "...",
      "database_name": "...",
      "database_id": "..."
    }
  ],
  "assets": [
    {
      "binding": "SWAGGER_JS",
      "directory": "./swagger",
      "pattern": "*.js"
    },
    {
      "binding": "SWAGGER_CSS",
      "directory": "./swagger",
      "pattern": "*.css"
    },
    {
      "binding": "SWAGGER_HTML",
      "directory": "./swagger",
      "pattern": "*.html"
    },
    {
      "binding": "SWAGGER_YAML",
      "directory": "./swagger",
      "pattern": "*.yaml"
    }
  ]
}

{
  "name": "api",
  "main": "v1/index.ts",
  "compatibility_date": "2025-04-05",
  "d1_databases": [
    {
      "binding": "...",
      "database_name": "...",
      "database_id": "..."
    }
  ],
  "assets": [
    {
      "binding": "SWAGGER_JS",
      "directory": "./swagger",
      "pattern": "*.js"
    },
    {
      "binding": "SWAGGER_CSS",
      "directory": "./swagger",
      "pattern": "*.css"
    },
    {
      "binding": "SWAGGER_HTML",
      "directory": "./swagger",
      "pattern": "*.html"
    },
    {
      "binding": "SWAGGER_YAML",
      "directory": "./swagger",
      "pattern": "*.yaml"
    }
  ]
}

D

datacenterdude•4/10/25, 6:02 PM

Aw, I think I see it now. It needs assets > bindings > binding1 > binding2 > binding*

D

datacenterdude•4/10/25, 6:05 PM

Like so...

"assets": {
    "bindings": [
      {
        "binding": "SWAGGER_JS",
        "directory": "./swagger",
        "pattern": "*.js"

"assets": {
    "bindings": [
      {
        "binding": "SWAGGER_JS",
        "directory": "./swagger",
        "pattern": "*.js"

"assets": {
    "bindings": [
      {
        "binding": "SWAGGER_JS",
        "directory": "./swagger",
        "pattern": "*.js"

"assets": {
    "bindings": [
      {
        "binding": "SWAGGER_JS",
        "directory": "./swagger",
        "pattern": "*.js"

And nope, that didn't get it done either. Stuck here.

D

datacenterdude•4/10/25, 6:16 PM

Figured it out. Had to be in this format:

 "assets": {
    "directory": "./swagger",
    "binding": "SWAGGER"
  }

 "assets": {
    "directory": "./swagger",
    "binding": "SWAGGER"
  }

 "assets": {
    "directory": "./swagger",
    "binding": "SWAGGER"
  }

 "assets": {
    "directory": "./swagger",
    "binding": "SWAGGER"
  }

D

datacenterdude•4/10/25, 6:19 PM

Turns out I was just overcomplicating things. Doesn't sound like me at all.

S

Samantas5855•4/10/25, 9:55 PM

are there issues with the caching in cloudflare pages?

K

Kiwi•4/10/25, 10:29 PM

Has anyone got a public repo they can share which shows a good Workers + Hono + BetterAuth implementation with a React Client?

L

LordSilver•4/10/25, 10:51 PM

where is the code editor for workers?

LLordSilver where is the code editor for workers?

K

Kiwi•4/10/25, 11:09 PM

On the website? Click into a worker then its an icon in top-right

L

LordSilver•4/10/25, 11:24 PM

ah got it thx

L

LordSilver•4/10/25, 11:25 PM

how do you install modules from the browser?

LLordSilver how do you install modules from the browser?

I

Isaac McFadyen•4/10/25, 11:26 PM

You can't, you need to use Wrangler

L

LordSilver•4/10/25, 11:27 PM

i see...

L

LordSilver•4/10/25, 11:27 PM

btw, is there a limit for how long a worker with browser rendering api can run?

L

LordSilver•4/10/25, 11:27 PM

i mean, i know the new timeout is 5min per run, but can i keep executing it 24/7? like a call every 10s

L

LordSilver•4/10/25, 11:28 PM

it's not clear to me what this means

L

LordSilver•4/10/25, 11:28 PM

like you can have 3 conrurent browsers per account

L

LordSilver•4/10/25, 11:28 PM

so i can theoretically run a browser all day

A

Avi•4/11/25, 1:05 AM

can someone explain the

1042

1042 work-to-worker limitation to me?

A

Avi•4/11/25, 1:06 AM

i dont understand why it exists - and if it does, why adding a custom domain "works around it"

A

Avi•4/11/25, 1:06 AM

what's the harm in making a worker-to-worker

fetch()

fetch()

?

A

Avi•4/11/25, 1:06 AM

its quite useful for e.g. building a reverse proxy

AAvi i dont understand why it exists - and if it does, why adding a custom domain "wo...

C

Chaika•4/11/25, 1:13 AM

the very short answer comes down to workers not being a proper origin, and the way requests are routed

the better solution nowadays by far is to use Service Bindings: https://developers.cloudflare.com/workers/runtime-apis/bindings/service-bindings/ which have no extra latency, and can be used with RPC for a lot nicer experience/more secure/just better

the long/full answer is: https://community.cloudflare.com/t/issue-with-worker-to-worker-https-request/94472/8

C

Chaika•4/11/25, 1:14 AM

worth highlighting the worker to worker restriction is only a thing within a single zone/domain, you can fetch other people's workers/etc no problem

L

LordSilver•4/11/25, 2:02 AM

how is it possible that code from cloudflare docs isn't working

L

LordSilver•4/11/25, 2:02 AM

https://developers.cloudflare.com/browser-rendering/platform/playwright/#take-a-screenshot

Cloudflare Docs

Playwright · Browser Rendering docs

Learn how to use Playwright with Cloudflare Workers for browser automation. Access Playwright API, manage sessions, and optimize browser rendering.

L

LordSilver•4/11/25, 2:02 AM

L

LordSilver•4/11/25, 2:27 AM

how do u deploy ts files to a worker

L

LordSilver•4/11/25, 2:28 AM

i think wrangler may do something in the background that terraform/pulumi doesn't do

LLordSilver how do u deploy ts files to a worker

H

Hello, I’m Allie!•4/11/25, 2:29 AM

You need to transpile it to JS somehow

H

Hello, I’m Allie!•4/11/25, 2:30 AM

wrangler does it with esbuild, but there are other options too

L

LordSilver•4/11/25, 2:34 AM

Can you give the full command?

L

LordSilver•4/11/25, 2:34 AM

Because there are tons of options

CChaika the very short answer comes down to workers not being a proper origin, and the w...

A

Avi•4/11/25, 2:36 AM

the "long answer" makes a lot of sense. it seems its really not a security thing at all, more of an ambiguity about intention - "going through the front door" vs going straight to the worker

A

Avi•4/11/25, 2:36 AM

i don't totally understand waht an "origin" specifically is for a worker

A

Avi•4/11/25, 2:37 AM

i think of origin as, e.g., you have a CDN and the "origin" is the server for the underlying asset

A

Avi•4/11/25, 2:37 AM

If they’re on the same zone, then the first worker’s subrequest would go to the “origin”, which doesn’t exist for workers.dev

A

Avi•4/11/25, 2:37 AM

i don't really understand this sentence

LLordSilver Can you give the full command?

H

Hello, I’m Allie!•4/11/25, 2:42 AM

For transpiling? It depends on what you want to use to transpile with

L

LordSilver•4/11/25, 2:47 AM

i could do it with esbuild but it's a mess

AAvi i don't totally understand waht an "origin" specifically is for a worker

C

Chaika•4/11/25, 2:47 AM

The simple idea is an "origin server" is the actual web server(s) behind Cloudflare, that it requests for content.
In the concept of Workers, a Worker on a route isn't considered a true origin server. After all, you can modify the incoming request and then pass it to the origin
Custom Domains make your worker an actual "Origin", sort of/essentially...

If they’re on the same zone, then the first worker’s subrequest would go to the “origin”, which doesn’t exist for workers.dev

It makes some more sense in the full content of the post. The first worker is fetching another worker. It goes through the worker on the same-zone subrequest and tries to request the "origin" which doesn't exist, so it errors

L

LordSilver•4/11/25, 2:47 AM

it generates a file with 80k lines