Hi everyone! It's the @Wrangler office hours, feel free to post any questions you have in this chan

D

Dr. Software•6/2/25, 4:04 PM

how about some wrangler plushies or merch

Z

zido•6/2/25, 4:04 PM

can you give an estimate timeline for python workers

K

Kanui•6/2/25, 4:05 PM

What are the biggest architectural or performance limitations you're currently facing with Wrangler and Workers, and how are you planning to address them for large-scale or monorepo projects?

P

Prae•6/2/25, 4:05 PM

The ability to track where out of the 1000 max subrequests we are at would be nice.

VVero Hi everyone! It's the @Wrangler office hours, feel free to post any questions y...

P

Peppy•6/2/25, 4:06 PM

Alright thanks!

R

Rohan Vashisht•6/2/25, 4:06 PM

When I deploy a project on Cloudflare Pages that includes Git submodules, does Cloudflare Pages automatically fetch and update those submodules to their latest commits during deployment?

M

mjraval•6/2/25, 4:07 PM

When deploying versions for an individual PR, is there a way to supply it's own env var for runtime. I am using GH Actions for deploy. Where BuildTime env Vars can be controlled but run time where I would like to specify for each version.

P

Prae•6/2/25, 4:07 PM

Removing github accounts from pages/works without deleting the worker/pages

L

Luke•6/2/25, 4:08 PM

Hey

I've been trying to profile my worker locally using the chrome perf tooling but the data coming back seems wildly incorrect (assuming because workers doesn't allow for accurate timings). Is there anything I can do locally to make these profiles more accurate?

e.g - Since the clock seems to update on IO i was considering doing a fetch request to a worker every 10ms to roughly update the clock but the outbound limit is too low.

P

piffie•6/2/25, 4:10 PM

Is there a good way to debug RPC on localhost? i only see connected, or not connected. no support in debugging or where the issue can be. funny enough: same code works on our remote environment - but not localhost.

S

sneakyf1shy•6/2/25, 4:15 PM

Is there any timeline or more info on containers?

Ssneakyf1shy Is there any timeline or more info on containers? 👀

J

James Opstad•6/2/25, 4:16 PM

Have you seen https://blog.cloudflare.com/cloudflare-containers-coming-2025/ ?

The Cloudflare Blog

Simple, scalable, and global: Containers are coming to Cloudflare W...

Cloudflare Containers are coming this June. Run new types of workloads on our network with an experience that is simple, scalable, global and deeply integrated with Workers.

J

James•6/2/25, 4:17 PM

Any news or progress you can share on the typegen with

wrangler types

wrangler types

wrangler types

wrangler types becoming more cohesive with

@types/node

@types/node

@types/node

@types/node? All the time the typegen doesn't actually match runtime behaviour here and include real nodejs_compat types, it just causes more problems in my experience, especially when you introduce third party libs that still have to use

workers-types

workers-types

workers-types

workers-types.

X

Xld3•6/2/25, 4:29 PM

I have some feedback for Pages to Workers migration. If you're serving static assets without going through a worker first, you should remove the [assets]binding="" from wrangler.toml. It would be nice to see this in the migration guide, I would think more often than not, a Pages project will be migrated to a static worker + multiple workers, or by just compiling Page Functions into one worker.

name = 'sh8r-static'
[assets]
directory = "dist"
not_found_handling = "404-page"

P

pseudonymous•6/2/25, 4:33 PM

Thank you for all that you do

Q

Queen Elizabeth II•6/2/25, 5:02 PM

why does wrangler tend to not print actual errors? like you need to catch and console.log for the trace and the text to be anything useful

D

Danylo Hotvianskyi•6/2/25, 7:50 PM

Is there are any way to inject template variables or env vars to wrangler.jsonc?

B

Brett Willis•6/2/25, 7:53 PM

I'd like to be able to specify the Cloudflare account via the CLI when deploying a Pages project.
Like you can specify it in wrangler.toml for Workers projects. But for Pages projects, if you have multiple accounts, you have to choose one interactively and cannot specify it on the CLI.

BBrett Willis I'd like to be able to specify the Cloudflare *account* via the CLI when deployi...

H

Hard@Work•6/2/25, 8:03 PM

Does

CLOUDFLARE_ACCOUNT_ID

CLOUDFLARE_ACCOUNT_ID

CLOUDFLARE_ACCOUNT_ID

CLOUDFLARE_ACCOUNT_ID work?

HHard@Work Does `CLOUDFLARE_ACCOUNT_ID` work?

B

Brett Willis•6/2/25, 9:29 PM

Looks like it works, was looking for CLI arguments not env variables so thanks for pointing it out!

O

Oz•6/3/25, 12:13 AM

Any idea on the timeline for worker aliases? (Like Pages aliases, branch name = url prefix)

A

Abrahem•6/3/25, 2:01 AM

:this:

<

<@235148962103951360>•6/3/25, 2:59 AM

is there a way to run multiple workers together with different routes locally with wrangler?

�

💀WOMBOVERSE💀•6/3/25, 4:11 AM

G

grrowl•6/3/25, 10:05 AM

Why not deploy to prod if that’s what you want

K

KelvTan•6/3/25, 11:43 AM

Thanks

J

James•6/3/25, 12:34 PM

One I forgot to raise yesterday during office hours @petebd, but are the daily workers-types releases even without any changes intentional?

OOz Any idea on the timeline for worker aliases? (Like Pages aliases, branch name = ...

P

petebd•6/3/25, 12:47 PM

This quarter

A

ALECKS•6/3/25, 6:03 PM

I have a worker that I run through the vite plugin, so locally with

vite dev

vite dev

vite dev

vite dev. The problem is that this worker is a "child" binding in a parent router, and when it starts up, the parent

wrangler dev

wrangler dev

wrangler dev

wrangler dev does not see it. Is there any way to get this working?

EEdmund Hung Do you mean the worker running in wrangler dev has a service binding to another ...

A

ALECKS•6/3/25, 6:48 PM

Yes, that's the use case. I did have the latest plugin, 1.4.0, and it's not working. My top level wrangler:

{
  "name": "router",
  "main": "apps/dev-router/src/index.ts",
  "compatibility_date": "2025-04-03",
  "workers": {
    "dash": "apps/dash/wrangler.jsonc",
    "api": "apps/server/wrangler.jsonc"
  },

  "services": [
    {
      "binding": "DASHBOARD_SERVICE",
      "service": "dash"
    },
    {
      "binding": "API_SERVICE",
      "service": "api"
    }
  ],

  "dev": {
    "port": 8080,
    "local_protocol": "http"
  }
}

{
  "name": "router",
  "main": "apps/dev-router/src/index.ts",
  "compatibility_date": "2025-04-03",
  "workers": {
    "dash": "apps/dash/wrangler.jsonc",
    "api": "apps/server/wrangler.jsonc"
  },

  "services": [
    {
      "binding": "DASHBOARD_SERVICE",
      "service": "dash"
    },
    {
      "binding": "API_SERVICE",
      "service": "api"
    }
  ],

  "dev": {
    "port": 8080,
    "local_protocol": "http"
  }
}

{
  "name": "router",
  "main": "apps/dev-router/src/index.ts",
  "compatibility_date": "2025-04-03",
  "workers": {
    "dash": "apps/dash/wrangler.jsonc",
    "api": "apps/server/wrangler.jsonc"
  },

  "services": [
    {
      "binding": "DASHBOARD_SERVICE",
      "service": "dash"
    },
    {
      "binding": "API_SERVICE",
      "service": "api"
    }
  ],

  "dev": {
    "port": 8080,
    "local_protocol": "http"
  }
}

{
  "name": "router",
  "main": "apps/dev-router/src/index.ts",
  "compatibility_date": "2025-04-03",
  "workers": {
    "dash": "apps/dash/wrangler.jsonc",
    "api": "apps/server/wrangler.jsonc"
  },

  "services": [
    {
      "binding": "DASHBOARD_SERVICE",
      "service": "dash"
    },
    {
      "binding": "API_SERVICE",
      "service": "api"
    }
  ],

  "dev": {
    "port": 8080,
    "local_protocol": "http"
  }
}

it routes to either service. the api service shows up just fine, but not the dashboard, which I run with vite dev

A

ALECKS•6/3/25, 6:48 PM

A

ALECKS•6/3/25, 6:52 PM

no, it's a monorepo, each in their own workspace

�

💀WOMBOVERSE💀•6/3/25, 11:15 PM

�

💀WOMBOVERSE💀•6/3/25, 11:15 PM

Hello all

0

0x146231489231923•6/4/25, 6:33 AM

anyone knows how to list all workers? not only current project

C

cosbgn•6/4/25, 7:38 AM

On an mac running Monterey I can't start an app on the most recent wrangler version:

 ERROR  dyld[87080]: Symbol not found: (__ZNSt3__122__libcpp_verbose_abortEPKcz)


 ERROR    Referenced from: '/Users/x/dev/app/node_modules/@cloudflare/workerd-darwin-64/bin/workerd'
 ERROR    Expected in: '/usr/lib/libc++.1.dylib'
 ERROR  Failed to initialize wrangler bindings proxy write EPIPE

 ERROR  dyld[87080]: Symbol not found: (__ZNSt3__122__libcpp_verbose_abortEPKcz)


 ERROR    Referenced from: '/Users/x/dev/app/node_modules/@cloudflare/workerd-darwin-64/bin/workerd'
 ERROR    Expected in: '/usr/lib/libc++.1.dylib'
 ERROR  Failed to initialize wrangler bindings proxy write EPIPE

 ERROR  dyld[87080]: Symbol not found: (__ZNSt3__122__libcpp_verbose_abortEPKcz)


 ERROR    Referenced from: '/Users/x/dev/app/node_modules/@cloudflare/workerd-darwin-64/bin/workerd'
 ERROR    Expected in: '/usr/lib/libc++.1.dylib'
 ERROR  Failed to initialize wrangler bindings proxy write EPIPE

 ERROR  dyld[87080]: Symbol not found: (__ZNSt3__122__libcpp_verbose_abortEPKcz)


 ERROR    Referenced from: '/Users/x/dev/app/node_modules/@cloudflare/workerd-darwin-64/bin/workerd'
 ERROR    Expected in: '/usr/lib/libc++.1.dylib'
 ERROR  Failed to initialize wrangler bindings proxy write EPIPE

C

cosbgn•6/4/25, 7:39 AM

It worked till last week's version. Is this a bug or wrangler dropped support for Monterey?

C

cosbgn•6/4/25, 7:45 AM

Wrangler@4.16 seems to be the last version which doesn't throw this error

T

top kek•6/4/25, 3:15 PM

it says here that we can create secrets with the

-e

-e

-e

-e flag (it’s even mispelled) but it does not work, it instead tried to create a new worker with the name

<APP>-staging

<APP>-staging

<APP>-staging

<APP>-staging which has no bindings no nothing

T

top kek•6/4/25, 3:16 PM

how do you guys have different API keys for different environments? i just want my branches to have a different API key for a third party and it’s literally impossible with secrets lol

E

elVengador•6/4/25, 11:32 PM

Hello there, I have ad doubt regarding github actions and wrangler, I want to set some secrests, following the documentation I'm using:

secrets

secrets

secrets

secrets but it is not working, it returns an error

🔑 Uploading secrets...
  /usr/local/bin/npx wrangler secret bulk
  
   ⛅️ wrangler 4.18.0 (update available 4.19.1)
  ─────────────────────────────────────────────
  ✘ [ERROR] Required Worker name missing. Please specify the Worker name in your Wrangler configuration file, or pass it as an argument with `--name <worker-name>`

🔑 Uploading secrets...
  /usr/local/bin/npx wrangler secret bulk
  
   ⛅️ wrangler 4.18.0 (update available 4.19.1)
  ─────────────────────────────────────────────
  ✘ [ERROR] Required Worker name missing. Please specify the Worker name in your Wrangler configuration file, or pass it as an argument with `--name <worker-name>`

🔑 Uploading secrets...
  /usr/local/bin/npx wrangler secret bulk
  
   ⛅️ wrangler 4.18.0 (update available 4.19.1)
  ─────────────────────────────────────────────
  ✘ [ERROR] Required Worker name missing. Please specify the Worker name in your Wrangler configuration file, or pass it as an argument with `--name <worker-name>`

🔑 Uploading secrets...
  /usr/local/bin/npx wrangler secret bulk
  
   ⛅️ wrangler 4.18.0 (update available 4.19.1)
  ─────────────────────────────────────────────
  ✘ [ERROR] Required Worker name missing. Please specify the Worker name in your Wrangler configuration file, or pass it as an argument with `--name <worker-name>`

I coudn't find in the documentation where should I add --name into my github actions, I think if I'm using

cloudflare/wrangler-action@v3

cloudflare/wrangler-action@v3

cloudflare/wrangler-action@v3

cloudflare/wrangler-action@v3, is not required to create a .toml file, I've tried to set-up

--project-name

--project-name

--project-name

--project-name and

--name

--name

--name

--name but I couldn't solve it, how can I fix this error?

deploy:
    runs-on: ubuntu-latest
    permissions:
      contents: read
      deployments: write
    needs: [test] # Correct job name
    steps:
      - uses: actions/checkout@v4
      - uses: oven-sh/setup-bun@v2
      - run: bun i
      - run: bun run build
      - name: Publish
        uses: cloudflare/wrangler-action@v3
        with:
          apiToken: ${{ secrets.CLOUDFLARE_API_TOKEN }}
          accountId: ${{ secrets.CLOUDFLARE_ACCOUNT_ID }}
          # projectName: ${{ secrets.CLOUDFLARE_PROJECT_NAME }}
          command: pages deploy dist --project-name="$CLOUDFLARE_PROJECT_NAME" --name="$CLOUDFLARE_PROJECT_NAME"
          gitHubToken: ${{ secrets.GITHUB_TOKEN }}
          secrets: |
            ASTRO_DB_APP_TOKEN
            ASTRO_DB_REMOTE_URL
        env:
          ASTRO_DB_APP_TOKEN: ${{ secrets.ASTRO_DB_APP_TOKEN }}
          ASTRO_DB_REMOTE_URL: ${{ secrets.ASTRO_DB_REMOTE_URL }}

deploy:
    runs-on: ubuntu-latest
    permissions:
      contents: read
      deployments: write
    needs: [test] # Correct job name
    steps:
      - uses: actions/checkout@v4
      - uses: oven-sh/setup-bun@v2
      - run: bun i
      - run: bun run build
      - name: Publish
        uses: cloudflare/wrangler-action@v3
        with:
          apiToken: ${{ secrets.CLOUDFLARE_API_TOKEN }}
          accountId: ${{ secrets.CLOUDFLARE_ACCOUNT_ID }}
          # projectName: ${{ secrets.CLOUDFLARE_PROJECT_NAME }}
          command: pages deploy dist --project-name="$CLOUDFLARE_PROJECT_NAME" --name="$CLOUDFLARE_PROJECT_NAME"
          gitHubToken: ${{ secrets.GITHUB_TOKEN }}
          secrets: |
            ASTRO_DB_APP_TOKEN
            ASTRO_DB_REMOTE_URL
        env:
          ASTRO_DB_APP_TOKEN: ${{ secrets.ASTRO_DB_APP_TOKEN }}
          ASTRO_DB_REMOTE_URL: ${{ secrets.ASTRO_DB_REMOTE_URL }}

deploy:
    runs-on: ubuntu-latest
    permissions:
      contents: read
      deployments: write
    needs: [test] # Correct job name
    steps:
      - uses: actions/checkout@v4
      - uses: oven-sh/setup-bun@v2
      - run: bun i
      - run: bun run build
      - name: Publish
        uses: cloudflare/wrangler-action@v3
        with:
          apiToken: ${{ secrets.CLOUDFLARE_API_TOKEN }}
          accountId: ${{ secrets.CLOUDFLARE_ACCOUNT_ID }}
          # projectName: ${{ secrets.CLOUDFLARE_PROJECT_NAME }}
          command: pages deploy dist --project-name="$CLOUDFLARE_PROJECT_NAME" --name="$CLOUDFLARE_PROJECT_NAME"
          gitHubToken: ${{ secrets.GITHUB_TOKEN }}
          secrets: |
            ASTRO_DB_APP_TOKEN
            ASTRO_DB_REMOTE_URL
        env:
          ASTRO_DB_APP_TOKEN: ${{ secrets.ASTRO_DB_APP_TOKEN }}
          ASTRO_DB_REMOTE_URL: ${{ secrets.ASTRO_DB_REMOTE_URL }}

deploy:
    runs-on: ubuntu-latest
    permissions:
      contents: read
      deployments: write
    needs: [test] # Correct job name
    steps:
      - uses: actions/checkout@v4
      - uses: oven-sh/setup-bun@v2
      - run: bun i
      - run: bun run build
      - name: Publish
        uses: cloudflare/wrangler-action@v3
        with:
          apiToken: ${{ secrets.CLOUDFLARE_API_TOKEN }}
          accountId: ${{ secrets.CLOUDFLARE_ACCOUNT_ID }}
          # projectName: ${{ secrets.CLOUDFLARE_PROJECT_NAME }}
          command: pages deploy dist --project-name="$CLOUDFLARE_PROJECT_NAME" --name="$CLOUDFLARE_PROJECT_NAME"
          gitHubToken: ${{ secrets.GITHUB_TOKEN }}
          secrets: |
            ASTRO_DB_APP_TOKEN
            ASTRO_DB_REMOTE_URL
        env:
          ASTRO_DB_APP_TOKEN: ${{ secrets.ASTRO_DB_APP_TOKEN }}
          ASTRO_DB_REMOTE_URL: ${{ secrets.ASTRO_DB_REMOTE_URL }}

Solved: I setup in preCommands with:

wrangler pages secret put ASTRO_DB_APP_TOKEN

wrangler pages secret put ASTRO_DB_APP_TOKEN

wrangler pages secret put ASTRO_DB_APP_TOKEN

wrangler pages secret put ASTRO_DB_APP_TOKEN

J

Jacob•6/5/25, 12:40 AM

Working on cloudflare queues/workers. I noticed that when calling npx wrangler types that it pulls whats in the jsonc plus whats on the server/UI. Issue is sometimes your secrets are out of synch from whats in the UI and your local machine. A git push overrides whatever is there in the UI. The description of this wrangler command says it pulls it in from your bindings but it generates a bunch of old + new types for the ENV bindings of secrets store + standard secrets. Should i play with these config flags? https://developers.cloudflare.com/workers/wrangler/commands/#types

JJames Opstad Have you seen https://blog.cloudflare.com/cloudflare-containers-coming-2025/ ?

A

Avilaa•6/5/25, 12:48 AM

Will it be worth it? Will Cloudflare Containers stand out over platforms?

Y

yinxingmaiming6409•6/5/25, 1:30 PM

I don't understand why a worker can't use all the Node.js modules, so what powerful features can he achieve? Apart from forwarding requests and writing HTML. What else can he do?

S

SnowBall•6/5/25, 1:43 PM

hi

Hi everyone! It's the @Wrangler office hours, feel free to post any questions you have in this chan

Similar Threads

Similar Threads

Similar Threads