is there a way or workaround for npm being annoying about audit vulns for wrangler? or do i have to
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?
I@EXtremeExploit this user fixed it by running an update (seemingly NPM was caching old deps), try that?
Dyou can use overrides (npm also supports them) to manually request a newer version
Ei 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
DI can't seem to get the new process.env flag to work...I have this in my wrangler config:
Dfirst log prints
{}this is in the agent chat starter
AMight have to change compatibility date to
2025-03-10For me i have a worker and a remix app on cf runtime, worker is fine accessing vars from
For remix it works fine if i build, but not in dev. Im running
process.envFor remix it works fine if i build, but not in dev. Im running
remix vite:dev
Ssurprised it dosent use unjs cookie-es
SHello! How can I use the
--remote@cloudflare/vite-plugin
M#wrangler
Enew wrangler build dry run problem:
cli.js around here
seems to be related to this... workers-and-pages-discussions
TypeError: The "options" argument must be of type object. Received an instance of AbortController
cli.js around here
seems to be related to this... workers-and-pages-discussions
Ethis was via bun also
JHow did the wrangler action even publish with a break, it uses itself and all it's commands in CI and tests @penalosa 
Zi'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.wrangler/deploy/config.jsonwranger.jsonc
JLooks 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
https://github.com/cloudflare/workers-sdk/blob/fd9dff833870b768af34b391bb109782d86908bb/packages/wrangler/src/config/index.ts#L41-L50
Zthat 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
JNice, was that documented anywhere or in a changelog or something?
FAfter upgrading wrangler to 4.1.0 logs have stopped working for me completely. Bug?
NHow can I make
wrangler dev
HYou cannot
NOh
NCool, thanks. My workaround of using a script to put it in .dev.vars will live on then lol
Eupdate: 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
so it seems bun doesn't like it when you pass an abortcontroller into setTimeout
FNevermind. I can't reproduce it anymore.
JI was referring to this?
MRunning Wrangler locally, I'm told that my version is out of date, and that I should run:
However this brings the following error:
However this brings the following error:
IYou've got a trailing backtick there.
MOh god...
MIt's one of those days
MSorry to have wasted your time!
INo problem 
MOne more. Having updated to Wrangler 4, it tells me to change
node_compatnodejs_compatdev.tomlwrangler.tomlI'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_compatnode_compatnodejs_compatI 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_compatnode_compatOK 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_compatAlthough 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_compatnodejs_compatOh.......
MThanks, 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?
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?
HWrangler shouldn't be running in production? Wrangler is used for development/deployment, but once deployed, Wrangler doesn't touch anything
MRight, thanks, I think I thought Wrangler ran everywhere.
MI 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.