btw it’s not very obvious that those are two paths and not two steps of one path
btw it’s not very obvious that those are two paths and not two steps of one path
DIs there any migration guide?
PCloudflare Docs
Wrangler v4 is a major release focused on updates to underlying systems and dependencies, along with improvements to keep Wrangler commands consistent and clear. Unlike previous major versions of Wrangler, which were foundational rewrites and rearchitectures — Version 4 of Wrangler includes a much smaller set of changes. If you use Wrangler toda...
HBasically, it is dynamically generated based on your
wrangler@cloudflare/workers-types having to ship every combination of compatibility dates/compatibility flags, now you can just generate it yourself in one goHPlus of course keeping your binding types in sync
HI mean, the team will continue to update
@cloudflare/workers-types for the forseeable future, so if you don't need it, you don't have to move
Syou arent supposed to touch that file anyway. i personally like it very much
HYeah, I like it too, and have been using it for a few months now. But I think it's great that they give you both options
Sfor sure!
Sloc are a lie 
but yea importing from cf-types/compDate is fine too
but yea importing from cf-types/compDate is fine too
HI mean, theoretically Workers Types(the Package) is actually larger, it just doesn't count as LoC because it is gitignored
Ahttps://developers.cloudflare.com/workers/wrangler/system-environment-variables/
This page over here says the
Okay, now if I try to login with OAuth, the page freezes because the IP was blocked.
The IP was blocked because I was using service like Github Workspace.
Wrangler 4 is a mess and seriously stopping me work with Cloudflare Infrastructure. Can someone have a look and clear the things up?
What is the reason that a person cannot login with API_TOKEN? If you guys are blocking logging in with API_TOKEN, how
This is seriously a frustruating experience.
This page over here says the
CLOUDFLARE_API_TOKEN can be used. But if I use the variable then I get an error as ✘ [ERROR] You are logged in with an API Token. Unset the CLOUDFLARE_API_TOKEN in the environment to log in via OAuth.Okay, now if I try to login with OAuth, the page freezes because the IP was blocked.
The IP was blocked because I was using service like Github Workspace.
Wrangler 4 is a mess and seriously stopping me work with Cloudflare Infrastructure. Can someone have a look and clear the things up?
What is the reason that a person cannot login with API_TOKEN? If you guys are blocking logging in with API_TOKEN, how
wranglerThis is seriously a frustruating experience.
Cloudflare Docs
Local environment variables that can change Wrangler's behavior.
IWhat command are you running that is rejecting CLOUDFLARE_API_TOKEN?
AI used to work this way with
But none of the commands are working including
wrangler devwrangler dev --remoteBut none of the commands are working including
wrangler deploy
WYou can also just pass in —include-runtime=false and you’ll get just the Env types like before, if you prefer :)
Vwhen i try to update my wrangler i get an error thats "unfixable" and so now i cant update my wrangler
Va big text says "▲ [WARNING] The version of Wrangler you are using is now out-of-date.
Please update to the latest version to prevent critical errors.
Run
After installation, run Wrangler with
but when i run npm install --save-dev wrangler@4 i get this
up to date, audited 141 packages in 3s
19 packages are looking for funding
run
5 vulnerabilities (3 low, 2 moderate)
Some issues need review, and may require choosing
a different dependency.
Run
so i run npm audit to see whats going on and i get this
cookie <0.7.0
cookie accepts cookie name, path, and domain with out of bounds characters - https://github.com/advisories/GHSA-pxg6-pf52-xh8x
No fix available
node_modules/youch/node_modules/cookie
youch 2.0.4 - 3.3.3
Depends on vulnerable versions of cookie
node_modules/youch
miniflare <=0.0.0-fff677e35 >=3.20250204.0
Depends on vulnerable versions of youch
node_modules/miniflare
wrangler *
Depends on vulnerable versions of esbuild
Depends on vulnerable versions of miniflare
node_modules/wrangler
esbuild <=0.24.2
Severity: moderate
esbuild enables any website to send any requests to the development server and read the response - https://github.com/advisories/GHSA-67mh-4wv8-2f99
No fix available
node_modules/esbuild
5 vulnerabilities (3 low, 2 moderate)
Some issues need review, and may require choosing
a different dependency.
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."but when i run npm install --save-dev wrangler@4 i get this
up to date, audited 141 packages in 3s
19 packages are looking for funding
run
npm fund for details5 vulnerabilities (3 low, 2 moderate)
Some issues need review, and may require choosing
a different dependency.
Run
npm audit for details.so i run npm audit to see whats going on and i get this
npm audit report
cookie <0.7.0
cookie accepts cookie name, path, and domain with out of bounds characters - https://github.com/advisories/GHSA-pxg6-pf52-xh8x
No fix available
node_modules/youch/node_modules/cookie
youch 2.0.4 - 3.3.3
Depends on vulnerable versions of cookie
node_modules/youch
miniflare <=0.0.0-fff677e35 >=3.20250204.0
Depends on vulnerable versions of youch
node_modules/miniflare
wrangler *
Depends on vulnerable versions of esbuild
Depends on vulnerable versions of miniflare
node_modules/wrangler
esbuild <=0.24.2
Severity: moderate
esbuild enables any website to send any requests to the development server and read the response - https://github.com/advisories/GHSA-67mh-4wv8-2f99
No fix available
node_modules/esbuild
5 vulnerabilities (3 low, 2 moderate)
Some issues need review, and may require choosing
a different dependency.
GitHub
cookie accepts cookie name, path, and domain with out of bounds characters
GitHub
esbuild enables any website to send any requests to the development server and read the response
V(nvm i fixed it)
Vi did
npm update -g wranglerAI 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), I am still getting the same error which probably means there was some change in the Cloudflare APIs which is causing this issue.AGetting this error with all the versions of wrangler (probably) while logging in with OAuth.
AWith wrangler v4, do we still ned to set
"types": ["./worker-configuration.d.ts"] in the tsconfig?VYe I fixed it
VAnd I was using v3
KIt "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
That just sounds like you need to update the TypeScript version or
compilerOptions.target in tsconfig?
JIt's possible
rules aren't being applied to dynamic imports. Out of interest, does it work if you just import html from '../templates/foo.html' at the top of the file?
FHey 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:
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!
AHey 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
Fah, got what you meant. will try to clarify that you can do either of the steps
F@Skye thanks, I misread the table. I thought that it was one of the implemented APIs, not a mock-up.
FHi 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!
FThank you @penalosa
Eis 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
