You are only billed for CPU time so no. Yes you can write streams to R2, but you need the binding in

Ssathoro You are only billed for CPU time so no. Yes you can write streams to R2, but you...

L

LordSilver•5/11/25, 2:21 PM

i meant, u still need to set up the operation with the sdk, it's not like r2 will accept the lambda response like if it was a client

LLordSilver i meant, u still need to set up the operation with the sdk, it's not like r2 wil...

S

sathoroOP•5/11/25, 2:35 PM

... what? inside a worker it's 2 lines of code to upload it to R2. an SDK and lambda is not involved

S

sathoroOP•5/11/25, 2:36 PM

you can upload a response stream directly to R2

L

LordSilver•5/11/25, 4:53 PM

why jsonc is new the standard for wrangler?

L

LordSilver•5/11/25, 4:53 PM

in what way is it superior to toml?

K

Kotkoroid•5/11/25, 5:00 PM

Cleaner if you have more environments

L

LordSilver•5/11/25, 5:01 PM

can u show code snippets?

K

Kotkoroid•5/11/25, 5:02 PM

What do u mean

L

LordSilver•5/11/25, 5:05 PM

why so many warnings

L

LordSilver•5/11/25, 5:05 PM

LLordSilver Click to see attachment

I

Isaac McFadyen•5/11/25, 5:09 PM

?workers-node

S

SuperHelpflare•5/11/25, 5:09 PM

Cloudflare Workers (and Pages Functions) runs on the V8 JavaScript engine, the same one used in Google Chrome.

Workers is different from Node.js. This means that certain features built in to Node do not work in Workers and cannot be used.

These features are not available:
- any kind of filesystem, unless you use an in-memory polyfill
- incoming TCP connections (outgoing are available using the TCP Socket API)
- any kind of UDP connections, both incoming and outgoing

These features may be available with a polyfill or the
nodejs_compat
nodejs_compat
nodejs_compat
nodejs_compat flag:
- some built-in Node modules, such as

path

path

path

path,

buffer

buffer

buffer

buffer,

crypto

crypto

crypto

crypto, and others

IIsaac McFadyen ?workers-node

L

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

i used teh code from the example

I

Isaac McFadyen•5/11/25, 5:10 PM

What example?

L

LordSilver•5/11/25, 5:12 PM

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

L

LordSilver•5/11/25, 5:16 PM

is this redundant?

L

LordSilver•5/11/25, 5:19 PM

mmm ok i deployed it

S

sathoroOP•5/11/25, 5:19 PM

toml gets absolutely disgusting very quickly lol

L

LordSilver•5/11/25, 5:41 PM

how is it possible the trace shows 23s, while the worker actually returned after 12s?

L

LordSilver•5/11/25, 5:41 PM

something is off

LLordSilver how is it possible the trace shows 23s, while the worker actually returned after...

J

Javi•5/11/25, 5:55 PM

F

filyys•5/11/25, 6:54 PM

Hi, are alternative methods of reading local files in workers really that hard?

F

filyys•5/11/25, 6:55 PM

I'm not sure how to approach it as everything I try, doesn't work out

S

SuperHelpflare•5/11/25, 6:55 PM

Please do not post your question in multiple channels/post it multiple times per the rules at #

welcome-and-rules. It creates confusion for people trying to help you and doesn't get your issue or question solved any faster.

F

filyys•5/11/25, 6:56 PM

Sorry, I wasn't sure if my post was visible

F

filyys•5/11/25, 6:56 PM

Thanks for the answer though, it's definitely going to help

L

LordSilver•5/11/25, 7:00 PM

how can u enable JS rendering on browser rendering api for playwright?

L

LordSilver•5/11/25, 7:00 PM

i noticed it doesn't render the page if it requires JS

L

Lucas Delbel•5/11/25, 7:20 PM

Hello guys, does anyone have a suggestion on a fast and easy-to-implement solution to push notifications from the workers to the pages? Maybe a pub-sub, or websocket-based tool?

M

maguayo•5/12/25, 6:45 AM

I am aware Spain LaLiga blocks some Cloudflare IPs.. But do we have a list of blocks? If we had I could create a monitor checker or sometrhing to alert me.

S

SuperHelpflare•5/12/25, 6:49 AM

Please do not post your question in multiple channels/post it multiple times per the rules at #

welcome-and-rules. It creates confusion for people trying to help you and doesn't get your issue or question solved any faster.

T

Talaat•5/12/25, 8:30 AM

Hey Everyone
I have three production websites hosted on Cloudflare Pages
everything worked fine for the past year
all of a sudden builds have stopped
I have deployment hooks as well as control the pages deployment dashboard Via the Cloudflare API designed for pages (deploy, retry, delete deployments and so on)

any ideas as to why that might happen

sadly, i am a contractor and dont have access to the dashboard
i did check the cloudflare status page and no issues with pages

T

Talaat•5/12/25, 8:41 AM

issue solved

Cloudflare and GitHub had a new permissions request. Needed to allow read and write access.

Thanks

P

predaytor•5/12/25, 9:15 AM

Am I right, does Cloudflare now properly support stale-while-revalidate? It seems to be working! Am I dreaming?

cache-control: public, max-age=1, stale-while-revalidate=604800
cf-cache-status: UPDATING

cache-control: public, max-age=1, stale-while-revalidate=604800
cf-cache-status: UPDATING

cache-control: public, max-age=1, stale-while-revalidate=604800
cf-cache-status: UPDATING

cache-control: public, max-age=1, stale-while-revalidate=604800
cf-cache-status: UPDATING

P

predaytor•5/12/25, 9:21 AM

or I may have applied to beta earlier.. ehh I'm not sure

C

cdslash•5/12/25, 9:56 AM

Should the types generated by

pnpm wrangler types

pnpm wrangler types

pnpm wrangler types

pnpm wrangler types be available as ambient types without needing to reference the types in each file? I am finding that they are not, and I have to use

/// <reference path="../worker-configuration.d.ts" />

/// <reference path="../worker-configuration.d.ts" />

/// <reference path="../worker-configuration.d.ts" />

/// <reference path="../worker-configuration.d.ts" /> at the top of the file for them to work. My tsconfig, in case I'm misconfiguring:

{
  "files": [],
  "references": [
    {
      "path": "./tsconfig.node.json"
    },
    {
      "path": "./tsconfig.cloudflare.json"
    }
  ],
  "include": [
    "worker-configuration.d.ts"
  ],
  "compilerOptions": {
    "checkJs": true,
    "verbatimModuleSyntax": true,
    "skipLibCheck": true,
    "strict": true,
    "noEmit": true,
    "baseUrl": ".",
    "paths": {
      "@/*": [
        "./app/*"
      ]
    }
  }
}

{
  "files": [],
  "references": [
    {
      "path": "./tsconfig.node.json"
    },
    {
      "path": "./tsconfig.cloudflare.json"
    }
  ],
  "include": [
    "worker-configuration.d.ts"
  ],
  "compilerOptions": {
    "checkJs": true,
    "verbatimModuleSyntax": true,
    "skipLibCheck": true,
    "strict": true,
    "noEmit": true,
    "baseUrl": ".",
    "paths": {
      "@/*": [
        "./app/*"
      ]
    }
  }
}

{
  "files": [],
  "references": [
    {
      "path": "./tsconfig.node.json"
    },
    {
      "path": "./tsconfig.cloudflare.json"
    }
  ],
  "include": [
    "worker-configuration.d.ts"
  ],
  "compilerOptions": {
    "checkJs": true,
    "verbatimModuleSyntax": true,
    "skipLibCheck": true,
    "strict": true,
    "noEmit": true,
    "baseUrl": ".",
    "paths": {
      "@/*": [
        "./app/*"
      ]
    }
  }
}

{
  "files": [],
  "references": [
    {
      "path": "./tsconfig.node.json"
    },
    {
      "path": "./tsconfig.cloudflare.json"
    }
  ],
  "include": [
    "worker-configuration.d.ts"
  ],
  "compilerOptions": {
    "checkJs": true,
    "verbatimModuleSyntax": true,
    "skipLibCheck": true,
    "strict": true,
    "noEmit": true,
    "baseUrl": ".",
    "paths": {
      "@/*": [
        "./app/*"
      ]
    }
  }
}

Ccdslash Should the types generated by `pnpm wrangler types` be available as ambient type...

K

Kotkoroid•5/12/25, 10:40 AM

You need to import them in

compilerOptions.types

compilerOptions.types

compilerOptions.types

compilerOptions.types and not in

include

include

include

include.

B

ByteBeast•5/12/25, 11:14 AM

I have one table in which I have auth column when i query it and fetch into worker, value in that column it gets converted in to **. what is this and how can I get actual value?

B

ByteBeast•5/12/25, 11:22 AM

Anyone please help me its urgent

BByteBeast Anyone please help me its urgent

T

tadhglewis•5/12/25, 11:47 AM

Seems like a feature to me? Logs obfuscate secrets. You probably shouldn't be logging secrets

BByteBeast Anyone please help me its urgent

T

tadhglewis•5/12/25, 11:53 AM

Side note, Discord is mostly community driven. You should not expect support SLAs let alone a response in <7 minutes. If you want that, look into Enterprise billing.

B

ByteBeast•5/12/25, 11:58 AM

@Lewis Okay. thank for support

T

tadhglewis•5/12/25, 12:23 PM

To more directly answer your question: you should query your database directly (locally) to view the data OR use a different variable name when logging however I would strongly recommend against this if it's a production app or sensitive data

LLordSilver how is it possible the trace shows 23s, while the worker actually returned after...

R

Rui Figueira•5/12/25, 2:39 PM

can you report that in https://github.com/cloudflare/playwright/issues ?

GitHub

Issues · cloudflare/playwright

Playwright fork that works with Cloudflare Browser Rendering - Issues · cloudflare/playwright

LLordSilver is this redundant?

R

Rui Figueira•5/12/25, 2:40 PM

It's redundant if you use the

wrangler types

wrangler types

wrangler types

wrangler types (as described in https://developers.cloudflare.com/workers/languages/typescript/)

R

Rui Figueira•5/12/25, 2:40 PM

`

L

LaySheen 🇵🇸•5/12/25, 7:55 PM

Are search engines' crawler bots automatically blocked on Cloudflare Pages?

L

LaySheen 🇵🇸•5/12/25, 7:59 PM

Alright. Thanks a lot.

K

Kiwi•5/12/25, 10:02 PM

I've been fighting with Vitest and service bindings in my mono repo. Has anyone managed to get past

TypeError: The RPC receiver does not implement the method "getFoo".

TypeError: The RPC receiver does not implement the method "getFoo".

TypeError: The RPC receiver does not implement the method "getFoo".

TypeError: The RPC receiver does not implement the method "getFoo".?

// api/wrangler.jsonc
 "services": [{
     "binding": "FOO_SERVICE",
     "service": "my-services",
     "entrypoint": "FooService"
   },
   {
     "binding": "USERS_SERVICE",
     "service": "my-services",
     "entrypoint": "UsersService"
   }]`

// api/wrangler.jsonc
 "services": [{
     "binding": "FOO_SERVICE",
     "service": "my-services",
     "entrypoint": "FooService"
   },
   {
     "binding": "USERS_SERVICE",
     "service": "my-services",
     "entrypoint": "UsersService"
   }]`

// api/wrangler.jsonc
 "services": [{
     "binding": "FOO_SERVICE",
     "service": "my-services",
     "entrypoint": "FooService"
   },
   {
     "binding": "USERS_SERVICE",
     "service": "my-services",
     "entrypoint": "UsersService"
   }]`

// api/wrangler.jsonc
 "services": [{
     "binding": "FOO_SERVICE",
     "service": "my-services",
     "entrypoint": "FooService"
   },
   {
     "binding": "USERS_SERVICE",
     "service": "my-services",
     "entrypoint": "UsersService"
   }]`

// api/vitest.config.ts
export default defineWorkersProject(async () => {
 return {
   test: {
    // … more setup
     poolOptions: {
       workers: {
         wrangler: { configPath: `${__dirname}/wrangler.jsonc`, environment: 'test' },
         singleWorker: true,
         miniflare: {
           bindings: {
             TEST_MIGRATIONS: migrations,
             TEST_SEED_FILES: seedFiles,
           },
           serviceBindings: {
             USERS_SERVICE: { name: 'my-services', entrypoint: 'UsersService' },
             FOO_SERVICE: { name: 'my-services', entryPoint: 'FooService' },
           },
           workers: [
             { // built by globalSetup.ts, coped into this directory
               name: my-services',
               modules: true,
               scriptPath: './.test/workers/services/my_services/index.js',
               compatibilityDate: '2025-01-01',
               compatibilityFlags: ['nodejs_compat'],
             },
           ],
         },
       },
     },
   },
 };
});

// api/vitest.config.ts
export default defineWorkersProject(async () => {
 return {
   test: {
    // … more setup
     poolOptions: {
       workers: {
         wrangler: { configPath: `${__dirname}/wrangler.jsonc`, environment: 'test' },
         singleWorker: true,
         miniflare: {
           bindings: {
             TEST_MIGRATIONS: migrations,
             TEST_SEED_FILES: seedFiles,
           },
           serviceBindings: {
             USERS_SERVICE: { name: 'my-services', entrypoint: 'UsersService' },
             FOO_SERVICE: { name: 'my-services', entryPoint: 'FooService' },
           },
           workers: [
             { // built by globalSetup.ts, coped into this directory
               name: my-services',
               modules: true,
               scriptPath: './.test/workers/services/my_services/index.js',
               compatibilityDate: '2025-01-01',
               compatibilityFlags: ['nodejs_compat'],
             },
           ],
         },
       },
     },
   },
 };
});

// api/vitest.config.ts
export default defineWorkersProject(async () => {
 return {
   test: {
    // … more setup
     poolOptions: {
       workers: {
         wrangler: { configPath: `${__dirname}/wrangler.jsonc`, environment: 'test' },
         singleWorker: true,
         miniflare: {
           bindings: {
             TEST_MIGRATIONS: migrations,
             TEST_SEED_FILES: seedFiles,
           },
           serviceBindings: {
             USERS_SERVICE: { name: 'my-services', entrypoint: 'UsersService' },
             FOO_SERVICE: { name: 'my-services', entryPoint: 'FooService' },
           },
           workers: [
             { // built by globalSetup.ts, coped into this directory
               name: my-services',
               modules: true,
               scriptPath: './.test/workers/services/my_services/index.js',
               compatibilityDate: '2025-01-01',
               compatibilityFlags: ['nodejs_compat'],
             },
           ],
         },
       },
     },
   },
 };
});

// api/vitest.config.ts
export default defineWorkersProject(async () => {
 return {
   test: {
    // … more setup
     poolOptions: {
       workers: {
         wrangler: { configPath: `${__dirname}/wrangler.jsonc`, environment: 'test' },
         singleWorker: true,
         miniflare: {
           bindings: {
             TEST_MIGRATIONS: migrations,
             TEST_SEED_FILES: seedFiles,
           },
           serviceBindings: {
             USERS_SERVICE: { name: 'my-services', entrypoint: 'UsersService' },
             FOO_SERVICE: { name: 'my-services', entryPoint: 'FooService' },
           },
           workers: [
             { // built by globalSetup.ts, coped into this directory
               name: my-services',
               modules: true,
               scriptPath: './.test/workers/services/my_services/index.js',
               compatibilityDate: '2025-01-01',
               compatibilityFlags: ['nodejs_compat'],
             },
           ],
         },
       },
     },
   },
 };
});

T

TuChutya•5/13/25, 4:24 AM

Hello pro ..
Need a small help.

I created a normal html based result website... and imported with github.

But problem is when i updating data in html.. but it not auto update my website..

I need to redeploy every times

please help.

https://beu.pages.dev/

https://github.com/try-to-learn-now/beu/blob/main/result/script.js

Can any one help me.. in auto redeploy from my github after update

Thankyou and do not ban for link.

GitHub

beu/result/script.js at main · try-to-learn-now/beu

Contribute to try-to-learn-now/beu development by creating an account on GitHub.

You are only billed for CPU time so no. Yes you can write streams to R2, but you need the binding in

Similar Threads

Similar Threads

Similar Threads