Thanks. When you're next available, taking a look at the example @Silvan posted in https://canary.di

J

JamesOP•4/5/25, 10:00 PM

In the future, it might be preferrable to not enable things like this so quickly by default when the documentation/education/logs around it aren't complete yet

B

BumblebeeSquare•4/5/25, 10:00 PM

not sure where to post this but please...

can we please allow upload .env directly for build variables ? it is annoying we have to upload one by one thorugh the ui ( regular env var seems like support pasting dotenv) - when using sveltekit we have to provide them for build .. and i think in pages, all env variables are also used as build variables
is there an max limit for build variable for workers ? once my build var reach 50+ i got Initializing build environment... internal error occurred. Please retry your build. If this problem persists, contact Cloudflare support.

JJames Thanks. When you're next available, taking a look at the example @Silvan posted ...

S

Silvan•4/5/25, 10:02 PM

technically it makes 100% sense else i dont get how this would even work
but this needs to be documented very clearly in 1 place else its very hard to find the connection between all these things

J

JamesOP•4/5/25, 10:10 PM

If I'm reading correctly, it looks like the

404.html

404.html

traverses up to find one, but

index.html

index.html

doesn't in SPA mode, which might explain your weirdness @Silvan: https://github.com/cloudflare/workers-sdk/blob/d4c11710fd36286be8587379d659e19e91778777/packages/workers-shared/asset-worker/src/handler.ts#L867

J

JamesOP•4/5/25, 10:11 PM

I've not tested and haven't looked that closely at this code, but that looks like what it's doing

Z

zwily•4/6/25, 3:57 AM

i reran npx wrangler types to generate a new worker-configuration.d.ts, and instead of doing this:
interface Env {
...
}

it did:
declare namespace Cloudflare {
interface Env {
...
}
}
interface Env extends Cloudflare.Env {}

and now my env doesn't work anywhere... (context.cloudflare.env doesn't have any of my types on it) Has anyone run into this or know how to fix it? (this is in a remix app, but I've updated to wrangler 4 and been using it fine for a bit...)

I

IG•4/8/25, 12:44 PM

I'm having the exact problem. Spent an hour reading docs, forums, but didn't find any solution. Came here (discord) in hopes of fix, but seems you didn't get any help either. Not a good first impression for this tool..

K

klouzo35•4/8/25, 1:21 PM

Same, getting this error on WSL2

MMatalina I am running `wrangler dev` and I'm getting an `write EPIPE` error on windows WS...

V

Vero•4/8/25, 1:29 PM

Hi. I'm trying to escalate this internally. Can you please share replication steps?

V

Vero•4/8/25, 1:30 PM

Or you're just running

wrangler dev

wrangler dev

and getting that error?

MMatalina I'm just doing `wrangler dev` and getting this error. Everything works in 3.75 ...

V

Vero•4/8/25, 1:48 PM

thanks. I'm passing this internally

K

klouzo35•4/8/25, 2:50 PM

I rollback to 3.107.3 and it seems to work

P

petebd•4/8/25, 2:55 PM

What about 4.0.0?

P

petebd•4/8/25, 3:04 PM

And what about 3.108.0 @klouzo35 ?

Ppetebd And what about 3.108.0 @klouzo35 ?

K

klouzo35•4/8/25, 3:19 PM

With the 4.0.0 I have the error but not with 3.108.0

K

klouzo35•4/8/25, 3:23 PM

Also I tested with 3.114.4 and the error was there

Ppenalosa @klouzo35 if you have a reproduction set up, I wonder if you'd be able to test w...

J

JamesOP•4/8/25, 4:40 PM

I can repro in my environment if you want to dig in, Samuel, just lemme know

Ppenalosa @klouzo35 if you have a reproduction set up, I wonder if you'd be able to test w...

J

JamesOP•4/8/25, 4:42 PM

`3.108.0` throws a more detailed error: ```✘ [ERROR] /home/cherry/.npm/_npx/a49ae4159d496e8f/node_modules/@cloudflare/workerd-linux-64/bin/workerd: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by /home/cherry/.npm/_npx/a49ae4159d496e8f/node_modules/@cloudflare/workerd-linux-64/bin/workerd)/home/cherry/.npm/_npx/a49ae4159d496e8f/node_modules/@cloudflare/workerd-linux-64/bin/workerd:/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by/home/cherry/.npm/_npx/a49ae4159d496e8f/node_modules/@cloudflare/workerd-linux-64/bin/workerd)/home/cherry/.npm/_npx/a49ae4159d496e8f/node_modules/@cloudflare/workerd-linux-64/bin/workerd:/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by/home/cherry/.npm/_npx/a49ae4159d496e8f/node_modules/@cloudflare/workerd-linux-64/bin/workerd)/home/cherry/.npm/_npx/a49ae4159d496e8f/node_modules/@cloudflare/workerd-linux-64/bin/workerd:/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.35' not found (required by/home/cherry/.npm/_npx/a49ae4159d496e8f/node_modules/@cloudflare/workerd-linux-64/bin/workerd)```

J

JamesOP•4/8/25, 4:42 PM

3.114.4 throws the same detailed error

J

JamesOP•4/8/25, 4:46 PM

3.103.2 is the last version that works for me here. 3.105.0 is where it starts throwing.

Ppenalosa What OS version is this? That looks like the error for Ubuntu 20 (which had supp...

J

JamesOP•4/8/25, 4:47 PM

Oh, yeah this is 20

V

Vero•4/8/25, 4:48 PM

thank youu

J

JamesOP•4/8/25, 4:53 PM

okay fwiw I can repro with ubuntu 24 too. Happy to retest once the new version is out

J

JamesOP•4/8/25, 4:58 PM

Can do, sec

M

Mitya•4/8/25, 5:00 PM

Hi - I've switched to using wrangler.json from wrangler.toml and when I deploy I get the error:

"No environment found in configuration with name "stage"."

This is not true. Here's my (truncated) wrangler.json file:

{
    "name": "******",
    "main": "src/index.js",
    "compatibility_date": "2023-11-21",
    "nodejs_compat": true,
    "minify": false,
    "account_id": "*************",
    "env": {
        "stage": {
            "hyperdrive": [{

{
    "name": "******",
    "main": "src/index.js",
    "compatibility_date": "2023-11-21",
    "nodejs_compat": true,
    "minify": false,
    "account_id": "*************",
    "env": {
        "stage": {
            "hyperdrive": [{

{
    "name": "******",
    "main": "src/index.js",
    "compatibility_date": "2023-11-21",
    "nodejs_compat": true,
    "minify": false,
    "account_id": "*************",
    "env": {
        "stage": {
            "hyperdrive": [{

{
    "name": "******",
    "main": "src/index.js",
    "compatibility_date": "2023-11-21",
    "nodejs_compat": true,
    "minify": false,
    "account_id": "*************",
    "env": {
        "stage": {
            "hyperdrive": [{

Anyone tell what's up?

EEdmund Hung Can you try overriding the workerd version to `1.20250408.0` and see if it fix t...

J

JamesOP•4/8/25, 5:00 PM

that does appear to resolve it, thank you

M

Mitya•4/8/25, 5:05 PM

Anyone able to help? Bit of an urgent one for me - can't deploy ^^

P

petebd•4/8/25, 5:11 PM

Do you have a redirected config? @mitya?

M

Mitya•4/8/25, 5:12 PM

Nope. I had a TOML file, and everything worked fine. Then I converted it to JSON, and now I get errors.

M

Mitya•4/8/25, 5:13 PM

Here's the full error output:

loading secrets...
  /usr/local/bin/npx wrangler secret bulk --env stage
  
   ⛅️ wrangler 3.90.0 (update available 4.9.0)
  --------------------------------------------
  
  ▲ [WARNING] The version of Wrangler you are using is now out-of-date.
  
    Please update to the latest version to prevent critical errors.
    Run `npm install --save-dev wrangler@4` to update to the latest version.
    After installation, run Wrangler with `npx wrangler`.
  
  
  ▲ [WARNING] Processing wrangler configuration:
  
      - No environment found in configuration with name "stage".
        Before using `--env=stage` there should be an equivalent environment section in the configuration.
    
        Consider adding an environment configuration section to the wrangler.toml file:
        [env.stage]
    
  ✘ [ERROR] Required Worker name missing. Please specify the Worker name in wrangler.toml, or pass it as an argument with `--name <worker-name>`
  
  ✘ [ERROR] Required Worker name missing. Please specify the Worker name in wrangler.toml, or pass it as an argument with `--name <worker-name>`
  
  :wood:  Logs were written to "/home/runner/.config/.wrangler/logs/wrangler-2025-04-08_17-09-54_623.log"
  Error: The process '/usr/local/bin/npx' failed with exit code 1
Error: Failed to upload secrets.
Error: Action failed

loading secrets...
  /usr/local/bin/npx wrangler secret bulk --env stage
  
   ⛅️ wrangler 3.90.0 (update available 4.9.0)
  --------------------------------------------
  
  ▲ [WARNING] The version of Wrangler you are using is now out-of-date.
  
    Please update to the latest version to prevent critical errors.
    Run `npm install --save-dev wrangler@4` to update to the latest version.
    After installation, run Wrangler with `npx wrangler`.
  
  
  ▲ [WARNING] Processing wrangler configuration:
  
      - No environment found in configuration with name "stage".
        Before using `--env=stage` there should be an equivalent environment section in the configuration.
    
        Consider adding an environment configuration section to the wrangler.toml file:
        [env.stage]
    
  ✘ [ERROR] Required Worker name missing. Please specify the Worker name in wrangler.toml, or pass it as an argument with `--name <worker-name>`
  
  ✘ [ERROR] Required Worker name missing. Please specify the Worker name in wrangler.toml, or pass it as an argument with `--name <worker-name>`
  
  :wood:  Logs were written to "/home/runner/.config/.wrangler/logs/wrangler-2025-04-08_17-09-54_623.log"
  Error: The process '/usr/local/bin/npx' failed with exit code 1
Error: Failed to upload secrets.
Error: Action failed

loading secrets...
  /usr/local/bin/npx wrangler secret bulk --env stage
  
   ⛅️ wrangler 3.90.0 (update available 4.9.0)
  --------------------------------------------
  
  ▲ [WARNING] The version of Wrangler you are using is now out-of-date.
  
    Please update to the latest version to prevent critical errors.
    Run `npm install --save-dev wrangler@4` to update to the latest version.
    After installation, run Wrangler with `npx wrangler`.
  
  
  ▲ [WARNING] Processing wrangler configuration:
  
      - No environment found in configuration with name "stage".
        Before using `--env=stage` there should be an equivalent environment section in the configuration.
    
        Consider adding an environment configuration section to the wrangler.toml file:
        [env.stage]
    
  ✘ [ERROR] Required Worker name missing. Please specify the Worker name in wrangler.toml, or pass it as an argument with `--name <worker-name>`
  
  ✘ [ERROR] Required Worker name missing. Please specify the Worker name in wrangler.toml, or pass it as an argument with `--name <worker-name>`
  
  :wood:  Logs were written to "/home/runner/.config/.wrangler/logs/wrangler-2025-04-08_17-09-54_623.log"
  Error: The process '/usr/local/bin/npx' failed with exit code 1
Error: Failed to upload secrets.
Error: Action failed

loading secrets...
  /usr/local/bin/npx wrangler secret bulk --env stage
  
   ⛅️ wrangler 3.90.0 (update available 4.9.0)
  --------------------------------------------
  
  ▲ [WARNING] The version of Wrangler you are using is now out-of-date.
  
    Please update to the latest version to prevent critical errors.
    Run `npm install --save-dev wrangler@4` to update to the latest version.
    After installation, run Wrangler with `npx wrangler`.
  
  
  ▲ [WARNING] Processing wrangler configuration:
  
      - No environment found in configuration with name "stage".
        Before using `--env=stage` there should be an equivalent environment section in the configuration.
    
        Consider adding an environment configuration section to the wrangler.toml file:
        [env.stage]
    
  ✘ [ERROR] Required Worker name missing. Please specify the Worker name in wrangler.toml, or pass it as an argument with `--name <worker-name>`
  
  ✘ [ERROR] Required Worker name missing. Please specify the Worker name in wrangler.toml, or pass it as an argument with `--name <worker-name>`
  
  :wood:  Logs were written to "/home/runner/.config/.wrangler/logs/wrangler-2025-04-08_17-09-54_623.log"
  Error: The process '/usr/local/bin/npx' failed with exit code 1
Error: Failed to upload secrets.
Error: Action failed

M

Mitya•4/8/25, 5:15 PM

Not sure why it's talking about TOML when I don't have a TOML file

M

Mitya•4/8/25, 5:15 PM

As I say, this all worked fine before I switched to JSON

M

Mitya•4/8/25, 5:18 PM

This is so weird. It also says I'm using Wrangler 3.9, when my package.json has:

  "devDependencies": {
    "wrangler": "^4.6.0"
  },

  "devDependencies": {
    "wrangler": "^4.6.0"
  },

  "devDependencies": {
    "wrangler": "^4.6.0"
  },

  "devDependencies": {
    "wrangler": "^4.6.0"
  },

M

Mitya•4/8/25, 5:24 PM

Perhaps I'll ask in #workers-help

EEdmund Hung Can you try overriding the workerd version to `1.20250408.0` and see if it fix t...

C

camiaei•4/8/25, 5:25 PM

works for me on ubuntu 24.04.2 x86_64

MMitya This is so weird. It also says I'm using Wrangler 3.9, when my package.json has:...

P

petebd•4/8/25, 5:30 PM

Wrangler 3.90.0 doesn't support wrangler.json, which is probably the superficial cause of this error.

It looks to me like you are not actually running this from the correct directory?
The fact that it says that you are running 3.90 suggests that it is picking up the globally cached version. Are you definitely running

npx

npx

npx

npx from the directory containing the wrangler.json?

Or possibly you haven't correctly installed the local packages by running

npm i

npm i

npm i

npm i?

M

Mitya•4/8/25, 5:30 PM

I'm doing nothing different at all - all I've done is delete wrangler.toml and add wrangler.json

M

Mitya•4/8/25, 5:30 PM

Hmm, well everything runs locally

M

Mitya•4/8/25, 5:31 PM

And shows the correct Wrangler version etc.

Thanks. When you're next available, taking a look at the example @Silvan posted in https://canary.di

Similar Threads

Similar Threads

Similar Threads