Cloudflare Developers•10mo ago

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

@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...

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

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

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"
],

    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);

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

first log prints

{}

{}

, second prints what i expect

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

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

Might have to change compatibility date to

2025-03-10

2025-03-10

(not sure)

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

is there anything im missing?

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

surprised it dosent use unjs cookie-es

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

Hello! How can I use the

--remote

--remote

option with

@cloudflare/vite-plugin

@cloudflare/vite-plugin

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

#wrangler

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;
      }
    }
  }

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

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

this was via bun also

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

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

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

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

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

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

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

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

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

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

You cannot

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

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

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

Nevermind. I can't reproduce it anymore.

Ppenalosa Ah, that looks like a bug with wrangler-action secrets and Wrangler v4. We’ll ge...

JacobMGEvans•3/18/25, 4:01 PM

I was referring to this?

Mitya•3/18/25, 4:41 PM

Running Wrangler locally, I'm told that my version is out of date, and that I should run:

npm install --save-dev wrangler@4`

npm install --save-dev wrangler@4`

However this brings the following error:

npm ERR! code EINVALIDTAGNAME
npm ERR! Invalid tag name "4`" of package "wrangler@4`": Tags may not have any characters that encodeURIComponent encodes.

npm ERR! code EINVALIDTAGNAME
npm ERR! Invalid tag name "4`" of package "wrangler@4`": Tags may not have any characters that encodeURIComponent encodes.

MMitya Running Wrangler locally, I'm told that my version is out of date, and that I sh...

Isaac McFadyenOP•3/18/25, 4:42 PM

You've got a trailing backtick there.

Mitya•3/18/25, 4:44 PM

Oh god...

Mitya•3/18/25, 4:44 PM

It's one of those days

Mitya•3/18/25, 4:44 PM

Sorry to have wasted your time!

Isaac McFadyenOP•3/18/25, 4:46 PM

No problem

Mitya•3/18/25, 4:49 PM

One more. Having updated to Wrangler 4, it tells me to change

node_compat

node_compat

nodejs_compat

nodejs_compat

. Should I do this not only in my

dev.toml

dev.toml

but also

wrangler.toml

wrangler.toml

i.e. the TOML for the production version? Does production always use the latest Wrangler?

Mitya•3/18/25, 5:10 PM

I'm not sure what I'm doing wrong here but since updating my (global) Wrangler to @4, my Worker won't run locally. It advises me to add

node_compat

node_compat

. But a previous message told me to change

node_compat

node_compat

nodejs_compat

nodejs_compat

for use with v.4, which I did. What am I doing wrong?

Mitya•3/18/25, 5:14 PM

I don't have it installed in my project - I just use a global one. Let me see if uninstalling the global Wrangler and installing project-level Wrangler fixes it. But just to be clear, with v4, it should be

nodejs_compat

nodejs_compat

, not

node_compat

node_compat

, right?

Mitya•3/18/25, 5:16 PM

OK now I have project-level Wrangler 4. When I run the worker it throws a tonne of errors about Node compatibility and tells me to add

nodejs_compat

nodejs_compat

to my config, which is already there.

Mitya•3/18/25, 5:18 PM

Although ironically, at the start of the log output, it says

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

So I have messages telling me both to add

nodejs_compat

nodejs_compat

and also that

nodejs_compat

nodejs_compat

is invalid.

Mitya•3/18/25, 5:19 PM

Oh.......

Mitya•3/18/25, 5:21 PM

Thanks, that's fixed it! Really appreciate your help.

Could I just clarify one more thing. Wrangler is a dev dependency. But the config changes I'm making are for both dev and live. So how do I control/do I need to worry about which version of Wrangler runs in production?

MMitya Thanks, that's fixed it! Really appreciate your help. Could I just clarify one ...

Hard@Work•3/18/25, 5:24 PM

Wrangler shouldn't be running in production? Wrangler is used for development/deployment, but once deployed, Wrangler doesn't touch anything

Mitya•3/18/25, 5:29 PM

Right, thanks, I think I thought Wrangler ran everywhere.

Mitya•3/18/25, 5:30 PM

I assumed production used the same environment I had locally, in the same way that developing locally with PHP involves something like Apache, which is also on the live server.

MMitya I assumed production used the same environment I had locally, in the same way th...

Hard@Work•3/18/25, 6:17 PM

Sort of? Wrangler, under the hood, calls into Miniflare, which runs Workers in

workerd

workerd

workerd

workerd

does run in production, but the goal is for you to never need to care which version of

workerd

workerd

is running

} 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; } } }

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

Similar Threads

Similar Threads

Similar Threads