i did `npm update -g wrangler`

Ppenalosa To clarify, were these commands working with Wrangler v3?

A

ashutosh•3/14/25, 5:34 AM

I started getting this error about 1 or 2 week ago. I assumed that it was due to updated version or wrangler but now when I tried it with lower version of wrangler (i.e.

3.93.0

3.93.0

3.93.0

3.93.0), I am still getting the same error which probably means there was some change in the Cloudflare APIs which is causing this issue.

A

ashutosh•3/14/25, 5:37 AM

Getting this error with all the versions of wrangler (probably) while logging in with OAuth.

Screenshot_2025-03-14_at_11.06.43_AM.png

A

alex (he/him)•3/14/25, 6:25 AM

With wrangler v4, do we still ned to set

"types": ["./worker-configuration.d.ts"]

"types": ["./worker-configuration.d.ts"]

"types": ["./worker-configuration.d.ts"]

"types": ["./worker-configuration.d.ts"] in the tsconfig?

Ppenalosa We’ve deprecated v2 (which it sounds like you were using), so I’d definitely rec...

V

VeriHappyOP•3/14/25, 9:11 AM

Ye I fixed it

V

VeriHappyOP•3/14/25, 9:12 AM

And I was using v3

Original message was deleted

K

kian•3/14/25, 12:47 PM

It "just works" in Wrangler 4, but your IDE has no knowledge of what Wrangler supports anyhow.

That just sounds like you need to update the TypeScript version or

compilerOptions.target

compilerOptions.target

compilerOptions.target

compilerOptions.target in tsconfig?

J

James•3/14/25, 2:52 PM

It's possible

rules

rules

rules

rules aren't being applied to dynamic imports. Out of interest, does it work if you just

import html from '../templates/foo.html'

import html from '../templates/foo.html'

import html from '../templates/foo.html'

import html from '../templates/foo.html' at the top of the file?

F

Franco Romano Losada•3/14/25, 3:13 PM

Hey everyone, do you know if child_process support via unenv will be implemented? https://github.com/unjs/unenv?tab=readme-ov-file#:~:text=%E2%9C%85%20node%3Achild_process

According to the unenv repo its already supported but I have an issue with a dependency in a worker.

It says:

✘ [ERROR] Error in transcribeVideo: Error: [unenv] child_process.spawn is not
implemented yet!

A

Althaf•3/14/25, 3:23 PM

Hey like i have hosted my vite react app in cloudflare pages and honobackend in the cf workers and there is an issue like when i login the cookie is not present i chrome cookies but in request header it is availabe and also like when i try to logout the cookie is still on the request header and unable to logout on dev no issues. after some reserch i have found like if the front end and backend have different domains like "pages.dev" and "worker.dev" as browser will not save cookie . so is there is a fix for it like without custom domain on dev side the vite proxy works but on production it will not any fix for it

KKeebs btw it’s not very obvious that those are two paths and not two steps of one path

F

flashblaze•3/14/25, 3:39 PM

ah, got what you meant. will try to clarify that you can do either of the steps

Original message was deleted

F

Franco Romano Losada•3/14/25, 8:51 PM

@Skye thanks, I misread the table. I thought that it was one of the implemented APIs, not a mock-up.

F

Farhian•3/15/25, 12:10 AM

Hi guys, starting a few days ago, our CI pipeline publishing a worker started failing with this error. Any ideas why that might be? Thank you!

F

Farhian•3/15/25, 5:06 AM

Thank you @penalosa

E

EXtremeExploit•3/15/25, 3:15 PM

is there a way or workaround for npm being annoying about audit vulns for wrangler? or do i have to wait for wrangler to update to fix them?

VVeriHappy i did `npm update -g wrangler`

I

Isaac McFadyen•3/15/25, 3:27 PM

@EXtremeExploit this user fixed it by running an update (seemingly NPM was caching old deps), try that?

EEXtremeExploit is there a way or workaround for npm being annoying about audit vulns for wrangl...

D

DaniFoldi•3/15/25, 3:27 PM

you can use overrides (npm also supports them) to manually request a newer version

IIsaac McFadyen @EXtremeExploit this user fixed it by running an update (seemingly NPM was cachi...

E

EXtremeExploit•3/15/25, 4:06 PM

i did try this already, the versions wrangler depends on esbuild and cookie have the vulns, and i want to use overrides as less as possible, its not a big deal so i guess i will just wait

D

dan•3/15/25, 5:58 PM

I can't seem to get the new process.env flag to work...I have this in my wrangler config:

"compatibility_date": "2025-02-28",
"compatibility_flags": [
    "nodejs_compat",
    "nodejs_compat_populate_process_env"
],

"compatibility_date": "2025-02-28",
"compatibility_flags": [
    "nodejs_compat",
    "nodejs_compat_populate_process_env"
],

"compatibility_date": "2025-02-28",
"compatibility_flags": [
    "nodejs_compat",
    "nodejs_compat_populate_process_env"
],

"compatibility_date": "2025-02-28",
"compatibility_flags": [
    "nodejs_compat",
    "nodejs_compat_populate_process_env"
],

    console.log('process.env', process.env);
    console.log(agent.env.OPENAI_API_KEY);

    console.log('process.env', process.env);
    console.log(agent.env.OPENAI_API_KEY);

    console.log('process.env', process.env);
    console.log(agent.env.OPENAI_API_KEY);

    console.log('process.env', process.env);
    console.log(agent.env.OPENAI_API_KEY);

D

dan•3/15/25, 5:59 PM

first log prints

{}

{}

{}

{}, second prints what i expect

D

dan•3/15/25, 5:59 PM

this is in the agent chat starter

Ddan I can't seem to get the new process.env flag to work...I have this in my wrangle...

A

AlanB•3/15/25, 11:04 PM

Might have to change compatibility date to

2025-03-10

2025-03-10

2025-03-10

2025-03-10 (not sure)

A

AlanB•3/15/25, 11:08 PM

For me i have a worker and a remix app on cf runtime, worker is fine accessing vars from

process.env

process.env

, remix kinda
For remix it works fine if i build, but not in dev. Im running

remix vite:dev

remix vite:dev

remix vite:dev

remix vite:dev is there anything im missing?

S

Silvan•3/16/25, 6:17 PM

surprised it dosent use unjs cookie-es

S

smalltalk96•3/17/25, 1:25 AM

Hello! How can I use the

--remote

--remote

option with

@cloudflare/vite-plugin

@cloudflare/vite-plugin

@cloudflare/vite-plugin

@cloudflare/vite-plugin?

M

mysterious_dragon_70032•3/17/25, 4:41 PM

#wrangler

E

Ephemeros•3/17/25, 6:34 PM

new wrangler build dry run problem:

TypeError: The "options" argument must be of type object. Received an instance of AbortController

cli.js around here

 } finally {
    try {
      if (typeof vitest === "undefined") {
        process.disconnect?.();
      }
      await closeSentry();
      const controller = new AbortController();
      await Promise.race([
        Promise.allSettled(dispatcher?.requests ?? []),
        (0, import_promises32.setTimeout)(1e3, void 0, controller) // <<<< this?
        // Ensure we don't hang indefinitely
      ]).then(() => controller.abort());
    } catch (e7) {
      logger.error(e7);
      if (!cliHandlerThrew) {
        throw e7;
      }
    }
  }

 } finally {
    try {
      if (typeof vitest === "undefined") {
        process.disconnect?.();
      }
      await closeSentry();
      const controller = new AbortController();
      await Promise.race([
        Promise.allSettled(dispatcher?.requests ?? []),
        (0, import_promises32.setTimeout)(1e3, void 0, controller) // <<<< this?
        // Ensure we don't hang indefinitely
      ]).then(() => controller.abort());
    } catch (e7) {
      logger.error(e7);
      if (!cliHandlerThrew) {
        throw e7;
      }
    }
  }

 } finally {
    try {
      if (typeof vitest === "undefined") {
        process.disconnect?.();
      }
      await closeSentry();
      const controller = new AbortController();
      await Promise.race([
        Promise.allSettled(dispatcher?.requests ?? []),
        (0, import_promises32.setTimeout)(1e3, void 0, controller) // <<<< this?
        // Ensure we don't hang indefinitely
      ]).then(() => controller.abort());
    } catch (e7) {
      logger.error(e7);
      if (!cliHandlerThrew) {
        throw e7;
      }
    }
  }

 } finally {
    try {
      if (typeof vitest === "undefined") {
        process.disconnect?.();
      }
      await closeSentry();
      const controller = new AbortController();
      await Promise.race([
        Promise.allSettled(dispatcher?.requests ?? []),
        (0, import_promises32.setTimeout)(1e3, void 0, controller) // <<<< this?
        // Ensure we don't hang indefinitely
      ]).then(() => controller.abort());
    } catch (e7) {
      logger.error(e7);
      if (!cliHandlerThrew) {
        throw e7;
      }
    }
  }

seems to be related to this... workers-and-pages-discussions

E

Ephemeros•3/17/25, 6:34 PM

this was via bun also

J

JacobMGEvans•3/18/25, 1:31 AM

How did the wrangler action even publish with a break, it uses itself and all it's commands in CI and tests @penalosa

Z

zwily•3/18/25, 1:36 AM

i'm building an app with vite (react-router) and a wrangler.jsonc, and... man weird stuff happening... i've been trying to deploy with

--env staging

--env staging

, and it wasn't finding my env for some reason. and it turns out, it's because there's this file being written to

.wrangler/deploy/config.json

.wrangler/deploy/config.json

that has these contents:

{"configPath":"../../build/server/wrangler.json","auxiliaryWorkers":[]}%

{"configPath":"../../build/server/wrangler.json","auxiliaryWorkers":[]}%

which points to build/server/wrangler.json being written during the build process, which is a stripped down version of my

wranger.jsonc

wranger.jsonc

. what's going on here???

Zzwily i'm building an app with vite (react-router) and a wrangler.jsonc, and... man we...

J

JacobMGEvans•3/18/25, 2:49 AM

Looks like they are supporting JSONC by converting it to JSON, probably just stripping out the comments
https://github.com/cloudflare/workers-sdk/blob/fd9dff833870b768af34b391bb109782d86908bb/packages/wrangler/src/config/index.ts#L41-L50

JJacobMGEvans Looks like they are supporting JSONC by converting it to JSON, probably just str...

Z

zwily•3/18/25, 2:50 AM

that wasn't it... it turns out that the cloudflare vite plugin creates a new flattened wrangler.json, and you have to specify CLOUDFLARE_ENV during the vite build in order for it to build the right one

Zzwily that wasn't it... it turns out that the cloudflare vite plugin creates a new fla...

J

JacobMGEvans•3/18/25, 2:53 AM

Nice, was that documented anywhere or in a changelog or something?

F

flowwise•3/18/25, 7:12 AM

After upgrading wrangler to 4.1.0 logs have stopped working for me completely. Bug?

N

neoney•3/18/25, 12:54 PM

How can I make

wrangler dev

wrangler dev

use my system environment variables? It doesn't pull them automatically, I have to list them in .dev.vars, and I'd like to avoid that.

Nneoney How can I make `wrangler dev` use my system environment variables? It doesn't pu...

H

Hello, I’m Allie!•3/18/25, 1:23 PM

You cannot

N

neoney•3/18/25, 1:31 PM

Oh

N

neoney•3/18/25, 1:31 PM

Cool, thanks. My workaround of using a script to put it in .dev.vars will live on then lol

EEphemeros this was via bun also

E

Ephemeros•3/18/25, 2:18 PM

update: i made my script not use bun and it was fine

so it seems bun doesn't like it when you pass an abortcontroller into setTimeout

Ppenalosa Could you provide some more details? Is this local mode or remote mode? What ver...

F

flowwise•3/18/25, 3:00 PM

Nevermind. I can't reproduce it anymore.

Similar Threads

Similar Threads

Similar Threads