is this redundant?

L

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

mmm ok i deployed it

S

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

toml gets absolutely disgusting very quickly lol

L

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

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

L

LordSilverOP•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

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

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

L

LordSilverOP•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.

S

Silvan•5/13/25, 12:03 PM

Interesting i was playing with neverthrow but rpc typing completly breaks it :(

L

LordSilverOP•5/13/25, 1:33 PM

why you get all this stuff added ot your file?

L

LordSilverOP•5/13/25, 1:33 PM

5700 lines of useless definittions

L

LordSilverOP•5/13/25, 1:35 PM

how can they both be recommended

J

James•5/13/25, 1:41 PM

That's the new typegen stuff with

wrangler types

wrangler types

wrangler types

wrangler types. I'm personally not a big fan of it, but it's where things seem to be moving. I believe it causes more problems than what it sets out to solve - such as no

nodejs_compat

nodejs_compat

nodejs_compat

nodejs_compat, interop with libraries that do need to import from

workers-types

workers-types

workers-types

workers-types and now ending up with duplicate types, etc. so in all of my projects I'm still using

workers-types

workers-types

workers-types

workers-types and defining my

Env

Env

Env

Env manually.

L

LordSilverOP•5/13/25, 1:52 PM

looks like a mess yeah

L

LordSilverOP•5/13/25, 1:52 PM

and people shouldn't use wrangler in the first place, but real IaC like Terraform. except that current provider doesn't even support most stuff

L

LordSilverOP•5/13/25, 1:53 PM

this wrangler types + jsonc instead of toml, i see cloudflare going in wrong directions everywhere

L

LordSilverOP•5/13/25, 2:05 PM

so the old

wrangler types

wrangler types

wrangler types

wrangler types is now

wrangler types --include-runtime=false

wrangler types --include-runtime=false

wrangler types --include-runtime=false

wrangler types --include-runtime=false

L

LordSilverOP•5/13/25, 2:25 PM

why it always gets stuck when tearing down a remote preview?

L

LordSilverOP•5/13/25, 2:25 PM

it hangs forever

LLordSilver this wrangler types + jsonc instead of toml, i see cloudflare going in wrong dir...

A

Ashley•5/13/25, 5:09 PM

I agree on the types but TOML is a strange format, and everyone uses JSON or YAML, so it makes far more sense to just use what everyone else does - to begin with I fell over so many times because I ordered things wrong in TOML or something, it’s too easy to do, so saves people learning a new platform + a new format

S

Silvan•5/13/25, 5:39 PM

im honestly surprised they didnt use TS for configs. like yea sure its a code format but i do like my configs typed i cannot lie

S

Silvan•5/13/25, 5:39 PM

everything better than yaml tho

I

ItsWendell•5/13/25, 7:15 PM

Thrilled that my first PR for Cloudflare's wrangler just landed in v4.15.0!

This PR adds a new

--metafile

--metafile

--metafile

--metafile flag to the wrangler CLI. This outputs esbuild's metafile, which can then be used to easily analyze your Cloudflare Worker's bundle size!

Update wrangler to v6.15.0 or newer, then simply run:

npx wrangler deploy --dry-run --metafile=./meta.json && npx banal -M ./meta.json

npx wrangler deploy --dry-run --metafile=./meta.json && npx banal -M ./meta.json

npx wrangler deploy --dry-run --metafile=./meta.json && npx banal -M ./meta.json

npx wrangler deploy --dry-run --metafile=./meta.json && npx banal -M ./meta.json (or add to your package.json file as

analyze

analyze

analyze

analyze).

This command uses banal – it's a great tool by fabiospampinato that provides an offline version of esbuild's web analyzer. Makes peeking into your bundle super easy!

LLordSilver this wrangler types + jsonc instead of toml, i see cloudflare going in wrong dir...

K

Kiwi•5/13/25, 8:25 PM

I really think CF is the dog who caught the car. The offering is really promising, but it's not quite there yet.

Similar Threads

Similar Threads

Similar Threads