Looks like they are supporting JSONC by converting it to JSON, probably just stripping out the comme

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

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

JacobMGEvansOP•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 McFadyen•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 McFadyen•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.tomldev.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 workerdworkerd. workerdworkerd does run in production, but the goal is for you to never need to care which version of workerdworkerd is running

nikiv.dev•3/18/25, 10:05 PM

does workers with wrangler support BufferBuffer?

James•3/18/25, 10:05 PM

yes

James•3/18/25, 10:05 PM

if you enable

nodejs_compat

nodejs_compat

nikiv.dev•3/18/25, 10:06 PM

nikiv.dev•3/18/25, 10:06 PM

how to get rid of this error, i installed types

nikiv.dev•3/18/25, 10:06 PM

https://github.com/nikitavoloboev/api-ts-hono

nikiv.dev•3/18/25, 10:07 PM

oh ok

nikiv.dev•3/18/25, 10:07 PM

i think its this

nikiv.dev•3/18/25, 10:10 PM

https://developers.cloudflare.com/changelog/2025-03-17-importable-env/ im confused

nikiv.dev•3/18/25, 10:10 PM

i can do this, but where to put the env

iano•3/19/25, 4:14 PM

Wrangler rewrites the request URL being sent to localhost into the custom domain which is set in wrangler.jsonc. Is that expected? It is very surprising to me?

iano•3/19/25, 4:15 PM

(So for example if I curl http://localhost:8787/ with a console.log in the fetch the fetch sees a request to url custom-domain.com even though its running locally)

jonasb•3/19/25, 8:19 PM

Hey

Now when wrangler@4 generates all the types, does anyone have guidance as to how to build libraries that depend on e.g. D1Database? For https://github.com/jonasb/d1-sql-tag I'm using @cloudflare/workers-types@cloudflare/workers-types , but get incompabilities when e.g. upgrading wrangler

GitHub

GitHub - jonasb/d1-sql-tag: A template literal for working with Clo...

A template literal for working with Cloudflare D1 database. - jonasb/d1-sql-tag

MSP2.Leaks•3/20/25, 12:26 PM

Who pinged me

Ppenalosa If you're using `@cloudflare/workers-types`, make sure you're using the `/experi...

echoes221•3/20/25, 3:00 PM

I've noticed that the types generated by wrangler 4.2.0 break on import when using Env as it extends cloudflare.env in the namespace, on 4.0.0 this is fine with no extension. Was this an accidental breaking change? When I say break, I mean that the values don't resolve to the namespace correctly after typegen.

Looks like they are supporting JSONC by converting it to JSON, probably just stripping out the comme

Similar Threads