i'm having the same issue too

U

usfOP•1/2/25, 10:46 PM

i reported in #workers-ai channel

Uusf i'm having the same issue too

S

snoob•1/2/25, 11:00 PM

oh thank god haha

S

snoob•1/2/25, 11:00 PM

yeah im like trying everything to figure out whats happening

M

Mitya•1/3/25, 10:12 AM

Out of nowhere I'm suddenly today getting this when I run

npm run dev

npm run dev

I've updated Wrangler to the latest version but no change. Anyone know what's behind this?

M

Mitya•1/3/25, 10:12 AM

The error is coming from within Wrangler, not my app, seemingly

M

Mitya•1/3/25, 11:49 AM

Restarting my system fixed it, though I'm not sure why

L

Lemon•1/4/25, 12:34 AM

Hey guys I'm tryna build and publish my pages in my monorepo (turborepo)
I have the following

workflow.yml

workflow.yml

workflow.yml

workflow.yml and properly setup the secrets as attached but I get the error that the env variables are missing.
Did anyone encountered something like this in a monorepo?

I console logged the value of the variables and its there but the CLI doesnt pick them up

for the build it runs

npm run build

npm run build

that runs build commands (like

astro build

astro build

astro build

astro build or

wrangler build

wrangler build

wrangler build

wrangler build for my workers with Hono) then

wrangler pages deploy ./dist

wrangler pages deploy ./dist

wrangler pages deploy ./dist

wrangler pages deploy ./dist or

wrangler deploy

wrangler deploy

for my workers...etc.

name: ⚡ Deploy to Cloudflare

on:
  push:
    branches:
      - master

jobs:
  deploy:
    runs-on: ubuntu-latest
    name: ☁️ Deploy
    steps:
      - name: 📥 Checkout
        uses: actions/checkout@v3

      - name: ⚙️ Use Node.js 18.x
        uses: actions/setup-node@v1
        with:
          node-version: 18.x

      - name: ⬇️ Install dependencies
        run: npm install

      - name: 🔨 Build apps & packages
        run: npm run build

      - name: 🚀 Deploy apps
        run: npm run deploy
        env:
          CLOUDFLARE_ACCOUNT_ID: ${{ secrets.CLOUDFLARE_ACCOUNT_ID }}
          CLOUDFLARE_API_TOKEN: ${{ secrets.CLOUDFLARE_API_TOKEN }}
          CLOUDFLARE_EMAIL: ${{ secrets.CLOUDFLARE_EMAIL }}

name: ⚡ Deploy to Cloudflare

on:
  push:
    branches:
      - master

jobs:
  deploy:
    runs-on: ubuntu-latest
    name: ☁️ Deploy
    steps:
      - name: 📥 Checkout
        uses: actions/checkout@v3

      - name: ⚙️ Use Node.js 18.x
        uses: actions/setup-node@v1
        with:
          node-version: 18.x

      - name: ⬇️ Install dependencies
        run: npm install

      - name: 🔨 Build apps & packages
        run: npm run build

      - name: 🚀 Deploy apps
        run: npm run deploy
        env:
          CLOUDFLARE_ACCOUNT_ID: ${{ secrets.CLOUDFLARE_ACCOUNT_ID }}
          CLOUDFLARE_API_TOKEN: ${{ secrets.CLOUDFLARE_API_TOKEN }}
          CLOUDFLARE_EMAIL: ${{ secrets.CLOUDFLARE_EMAIL }}

name: ⚡ Deploy to Cloudflare

on:
  push:
    branches:
      - master

jobs:
  deploy:
    runs-on: ubuntu-latest
    name: ☁️ Deploy
    steps:
      - name: 📥 Checkout
        uses: actions/checkout@v3

      - name: ⚙️ Use Node.js 18.x
        uses: actions/setup-node@v1
        with:
          node-version: 18.x

      - name: ⬇️ Install dependencies
        run: npm install

      - name: 🔨 Build apps & packages
        run: npm run build

      - name: 🚀 Deploy apps
        run: npm run deploy
        env:
          CLOUDFLARE_ACCOUNT_ID: ${{ secrets.CLOUDFLARE_ACCOUNT_ID }}
          CLOUDFLARE_API_TOKEN: ${{ secrets.CLOUDFLARE_API_TOKEN }}
          CLOUDFLARE_EMAIL: ${{ secrets.CLOUDFLARE_EMAIL }}

name: ⚡ Deploy to Cloudflare

on:
  push:
    branches:
      - master

jobs:
  deploy:
    runs-on: ubuntu-latest
    name: ☁️ Deploy
    steps:
      - name: 📥 Checkout
        uses: actions/checkout@v3

      - name: ⚙️ Use Node.js 18.x
        uses: actions/setup-node@v1
        with:
          node-version: 18.x

      - name: ⬇️ Install dependencies
        run: npm install

      - name: 🔨 Build apps & packages
        run: npm run build

      - name: 🚀 Deploy apps
        run: npm run deploy
        env:
          CLOUDFLARE_ACCOUNT_ID: ${{ secrets.CLOUDFLARE_ACCOUNT_ID }}
          CLOUDFLARE_API_TOKEN: ${{ secrets.CLOUDFLARE_API_TOKEN }}
          CLOUDFLARE_EMAIL: ${{ secrets.CLOUDFLARE_EMAIL }}

Original message was deleted

L

Lemon•1/6/25, 4:40 AM

Nah I pass
The action doesn’t support multiple folders afaik especially when running different commands ex for pages and workers there are two separate commands

I deploy 6 sites and the action is limited to 5 based on the docs
All I want is to make the stupid CLI work because it ain’t reading the env variable that is clearly present
It worked with a year ago but now that repo is broken too someone changed something…

Z

zecanard•1/6/25, 7:21 AM

Does anyone know how to upload metadata with

wrangler kv bulk put

wrangler kv bulk put

wrangler kv bulk put

wrangler kv bulk put? I tried following the docs, passing the following JSON:

[
    {
        "key": "key1",
        "value": "value1",
        "metadata": "{ \"metadata1\": 1 }"
    },
    {
        "key": "key2",
        "value": "value2",
        "metadata": "{ \"metadata2\": 2 }"
    }
]

[
    {
        "key": "key1",
        "value": "value1",
        "metadata": "{ \"metadata1\": 1 }"
    },
    {
        "key": "key2",
        "value": "value2",
        "metadata": "{ \"metadata2\": 2 }"
    }
]

[
    {
        "key": "key1",
        "value": "value1",
        "metadata": "{ \"metadata1\": 1 }"
    },
    {
        "key": "key2",
        "value": "value2",
        "metadata": "{ \"metadata2\": 2 }"
    }
]

[
    {
        "key": "key1",
        "value": "value1",
        "metadata": "{ \"metadata1\": 1 }"
    },
    {
        "key": "key2",
        "value": "value2",
        "metadata": "{ \"metadata2\": 2 }"
    }
]

But I get the following error:

⛅️ wrangler 3.99.0
-------------------

✘ [ERROR] Unexpected JSON input from "kv.json".

  Each item in the array should be an object that matches:
  
  interface KeyValue {
    key: string;
    value: string;
    expiration?: number;
    expiration_ttl?: number;
    metadata?: object;
    base64?: boolean;
  }
  
  The item at index 0 is {"key":"key1","value":"value1","metadata":"{ \"metadata1\": 1 }"}
  The item at index 1 is {"key":"key2","value":"value2","metadata":"{ \"metadata2\": 2 }"}

⛅️ wrangler 3.99.0
-------------------

✘ [ERROR] Unexpected JSON input from "kv.json".

  Each item in the array should be an object that matches:
  
  interface KeyValue {
    key: string;
    value: string;
    expiration?: number;
    expiration_ttl?: number;
    metadata?: object;
    base64?: boolean;
  }
  
  The item at index 0 is {"key":"key1","value":"value1","metadata":"{ \"metadata1\": 1 }"}
  The item at index 1 is {"key":"key2","value":"value2","metadata":"{ \"metadata2\": 2 }"}

⛅️ wrangler 3.99.0
-------------------

✘ [ERROR] Unexpected JSON input from "kv.json".

  Each item in the array should be an object that matches:
  
  interface KeyValue {
    key: string;
    value: string;
    expiration?: number;
    expiration_ttl?: number;
    metadata?: object;
    base64?: boolean;
  }
  
  The item at index 0 is {"key":"key1","value":"value1","metadata":"{ \"metadata1\": 1 }"}
  The item at index 1 is {"key":"key2","value":"value2","metadata":"{ \"metadata2\": 2 }"}

⛅️ wrangler 3.99.0
-------------------

✘ [ERROR] Unexpected JSON input from "kv.json".

  Each item in the array should be an object that matches:
  
  interface KeyValue {
    key: string;
    value: string;
    expiration?: number;
    expiration_ttl?: number;
    metadata?: object;
    base64?: boolean;
  }
  
  The item at index 0 is {"key":"key1","value":"value1","metadata":"{ \"metadata1\": 1 }"}
  The item at index 1 is {"key":"key2","value":"value2","metadata":"{ \"metadata2\": 2 }"}

What kind of

object

object

do we need to pass for the

metadata

metadata

? In contrast,

wrangler kv key put --metadata

wrangler kv key put --metadata

wrangler kv key put --metadata

wrangler kv key put --metadata does accept a JSON-serialized string and works as expected.

The

bulk put

bulk put

bulk put

bulk put works as expected if I just pass the

key

key

and

value

value

, or with the example provided in the docs (passing an

expiration_ttl

expiration_ttl

expiration_ttl

expiration_ttl).

J

James•1/6/25, 4:34 PM

wrangler adjacent with workers-types, but just want to make sure folks are aware of https://github.com/cloudflare/workerd/pull/3278. There's a whole bunch of proposed breaking changes there that need some more careful thought/consideration imo.

J

James•1/6/25, 4:53 PM

Thanks! There's countless examples of people using the types like

AiTextGenerationInput

AiTextGenerationInput

AiTextGenerationInput

AiTextGenerationInput, etc. so I'm looking forward to see the direction here. My 2c: it either needs to be a new major workers-types, or walked back so to be an extension of types instead of introducing breaking changes.

J

James•1/6/25, 4:54 PM

I'm not personally convinced a separate package makes sense, given how it bypasses all of the great OSS process in workers-types, not to mention is a

0.x.x

0.x.x

0.x.x

0.x.x version so RIP semver, which for a GA product is not great.

J

James•1/6/25, 4:54 PM

But thanks for the insight!

T

Torianna•1/6/25, 5:02 PM

in most codebases, using

any

any

is forbidden

T

Torianna•1/6/25, 5:04 PM

like, the whole point of types is to be typed, not bypassed with

any

any

J

Jürgen Leschner•1/6/25, 5:21 PM

Hi - I was wondering if there is anything you can share about vite environments and wrangler.
It would be really cool if vite-based dev frameworks could be nicely integrated with "regular" cloudflare workers for local dev workflows.

J

Jürgen Leschner•1/6/25, 5:32 PM

Related question (adjacent to wrangler) I was wondering if Cloudflare will also help to extend some of the other framework adapters e.g. @astro/cloudflare, to enable them to use features like Durable Objects. (Cloudflare adapter is unable to export D...)

J

Jürgen Leschner•1/6/25, 5:45 PM

connecting those 2 questions - i guess what I'm hoping is that adapters might get simpler if the new vite integration allowed for co-development of workers/DOs for server-side apis together with the front-end framework components that depend on those services.

Ppenalosa It's something we're actively working on! cc @James Opstad —what's the best plac...

L

Likeawinnaar•1/6/25, 5:46 PM

Pls loom to my ticket

L

Likeawinnaar•1/6/25, 5:46 PM

general-helpHelp needed

L

Likeawinnaar•1/6/25, 5:47 PM

Look*

J

Jürgen Leschner•1/6/25, 6:03 PM

(wee bit spammy in here today :blob_sweat: - thanks for taking the questions

)

JJürgen Leschner Hi - I was wondering if there is anything you can share about vite environments ...

J

James Opstad•1/6/25, 6:07 PM

We'll be releasing an official Vite plugin in the near future. If you're interested in tinkering with it while it's in progress, it's currently in this repo - https://github.com/flarelabs-net/vite-plugin-cloudflare.

GitHub

GitHub - flarelabs-net/vite-plugin-cloudflare

Contribute to flarelabs-net/vite-plugin-cloudflare development by creating an account on GitHub.

R

Rick•1/9/25, 6:24 AM

Can I have wrangler do an extra action before every server restart?
Right now, wrangler restarts server every time I save my updated source.
I want it to also rebuild the css using

npx @tailwindcss/cli -i input.css -o output.css

npx @tailwindcss/cli -i input.css -o output.css

npx @tailwindcss/cli -i input.css -o output.css

npx @tailwindcss/cli -i input.css -o output.css and then serve that

W

William•1/11/25, 6:11 PM

does anyone know if wrangler v3.101.0 works with pnpm? when I use npm as package manager, wrangler works fine, but when using pnpm as package manager, running wrangler in command line resulting in following error:

$ wrangler
file:///D:/development/indie_projects/cloudflare-d1-test/node_modules/.pnpm/readdirp@4.1.0/node_modules/readdirp/index.js:2
Object.defineProperty(exports, "__esModule", { value: true });
^

ReferenceError: exports is not defined
at file:///D:/development/indie_projects/cloudflare-d1-test/node_modules/.pnpm/readdirp@4.1.0/node_modules/readdirp/index.js:2:23
at ModuleJobSync.runSync (node:internal/modules/esm/module_job:395:35)
at ModuleLoader.importSyncForRequire (node:internal/modules/esm/loader:329:47)
at loadESMFromCJS (node:internal/modules/cjs/loader:1411:24)
at Module._compile (node:internal/modules/cjs/loader:1544:5)
at Object..js (node:internal/modules/cjs/loader:1668:16)
at Module.load (node:internal/modules/cjs/loader:1313:32)
at Function._load (node:internal/modules/cjs/loader:1123:12)
at TracingChannel.traceSync (node:diagnostics_channel:322:14)
at wrapModuleLoad (node:internal/modules/cjs/loader:217:24)

Node.js v22.13.0

J

James•1/11/25, 6:14 PM

Try a complete fresh install of wrangler - there was a bug in a transient dependency (

readdirp@4.1.0

readdirp@4.1.0

readdirp@4.1.0

readdirp@4.1.0) that caused this problem, but

4.1.1

4.1.1

4.1.1

4.1.1 has now been released to fix it

J

James•1/11/25, 6:14 PM

https://www.cloudflarestatus.com/incidents/flcv5ff4xbx8

Wrangler Installation Issue

J

James•1/11/25, 6:14 PM

https://github.com/paulmillr/readdirp/issues/203

W

William•1/11/25, 6:38 PM

@James Thanks, James! I finally got this resolved. I was so unlucky to encounter this problem the very first time I started using wrangler. But I’m so lucky to have your help—really appreciate it!

D

dom•1/13/25, 10:01 PM

When I add new log definintions to wrangler i get this error on deploy. Anyone have a solution?

[WARNING] Processing wrangler.toml configuration:

Unexpected fields found in top-level field: "observability"

Ive tried
[observability.logs]
enabled = true

or
[[observability.logs]]
enabled = true
or
[observability.logs]
enabled = true

K

kian•1/13/25, 10:01 PM

What Wrangler version are you using?

D

dom•1/13/25, 10:02 PM

hmm good question. i dont have a version defined in wrangler.toml. Where does one define the version?

K

kian•1/13/25, 10:02 PM

It isn't a TOML thing, Wrangler itself has a version associated with it when you install the CLI

D

dom•1/13/25, 10:02 PM

ah checking

K

kian•1/13/25, 10:03 PM

https://developers.cloudflare.com/workers/wrangler/install-and-update/#check-your-wrangler-version

D

dom•1/13/25, 10:03 PM

wrangler 3.62.0

D

dom•1/13/25, 10:04 PM

ill update thx

Mmiljussss Hello? Is this familiar to some of you? ✘ [ERROR] service core:user:worker: Unc...

A

Athestar•1/14/25, 1:43 AM

@miljussss Same to me, have you fixed your matter?

I

ItsWendell•1/15/25, 12:54 PM

Would be great if for debugging purposes we could somehow forcefully bind to a production bucket with

wrangler dev --remote

wrangler dev --remote

, if I try to do that right now I get the following error:

"✘ [ERROR] In development, you should use a separate r2 bucket than the one you'd use in production. Please create a new r2 bucket with "wrangler r2 bucket create <name>" and add its name as preview_bucket_name to the r2_buckets "R2_ASSETS_PUBLIC" in your wrangler.toml file"

It makes sense, but would be great to explicitly allow to bypass this.

IItsWendell Would be great if for debugging purposes we could somehow forcefully bind to a p...

H

Hello, I’m Allie!•1/15/25, 2:17 PM

Do you have a preview_bucket_name set? You should be able to just use the same bucket name twice

I

ItsWendell•1/15/25, 3:15 PM

Ohhh thanks, I completely misread this, thought I had to create a new bucket with a preview prefix, thanks, this works!

R

RaSk•1/17/25, 12:02 PM

Not sure if this is a right channel, can someone from Wrangler action team have a review at my PR?
It's less than 60s code review

This is a blocker for

cloudflare/pages-action

cloudflare/pages-action

cloudflare/pages-action

cloudflare/pages-action migration to

cloudflare/wrangler-action

cloudflare/wrangler-action

cloudflare/wrangler-action

cloudflare/wrangler-action

Note:

package-lock.json

package-lock.json

package-lock.json

package-lock.json is also out of date

I

imanlı supra•1/17/25, 12:12 PM

Hi! I want to get access for zero trust but I don't have a team can I get only for my self?

C

cg•1/17/25, 5:57 PM

x-posting

Hey all, is there a way to get the Pages build command to use a newer version of wrangler?
I've set the compat date in my wrangler.toml to 2025-01-17 however, the build step is still using:
09:26:56.234 Found Functions directory at /functions. Uploading.
09:26:56.241

wrangler 3.92.0

I'm trying to use 3.101.2 as I can doing a build on my local machine with that version, but the build/deployment is failing
My package.json specifies 3.101.2 as the wrangler version too
idk why 3.92 is being used

S

SuperHelpflare•1/17/25, 5:59 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.

Similar Threads