Can you reproduce with a fresh worker created via `npm create cloudflare@latest`?
Can you reproduce with a fresh worker created via
npm create cloudflare@latest
JIs there something specific in your worker or wrangler.toml that's causing it? I'd start by trying to reproduce with a simple worker and then going from there.
BHey folks, does anyone know what this error means? Specially the "make sure you've set the upstream option" part
HThis sounds like the Worker is calling itself in an infinite loop.
BWhat does upstream option mean ?
HThe
hostwranglerCloudflare Docs
Use a
wrangler.toml
Jin the end reopening iterm sorted it out. still seems strange for it to silently fail with no output. I guess maybe an issue with a wrangler process still running? or maybe something to do with deleting the 
.wrangler"have you tried turning it off and on again?"
J@James I spoke too soon, it's doing the same thing again..
Jsame issue happens in a fresh worker created with create-cloudflare
Jso seems to be wrangler getting into some kind of bad state
Jseems to be kind of non deterministic.. sometimes it works if I quit iterm and run
wrangler dev
Jdev server runs successfully. I press x to close it. I try to run it again.. no output
Jupgrading from node 18 to 21 and reinstalling wrangler seems to have sorted it for now..
DHello all. Just posted this in workers help in case anyone has a view: workers-and-pages-helpCustom Routes - Best Practice for Workers as Microservices
NI don't think I remember
wrangler tail
HDo you mean
wrangler tailoops, yeah I mean
wrangler tail
IYes. Cloudflare has a logging pipeline set up for all deployed Workers, so they can give you the logs live via
wrangler tailYou can also pipe them to an external destination via Workers Logpush (on a Workers paid plan).
Nfor all deployed workers, that's very cool
BHi All, has anyone been through this before ?
IIt looks like you're trying to run the JS file directly with Node? If so you'll need to use Wrangler.
IOr is this something else?
Bthis is my
.vscode/launch.json :BMy
tsconfigAnd my
package.jsonSo you're trying to run the Javascript file from
tsc directly.IThat won't work.
IYou'll need to run
wrangler dev(see your
start script)BI'm able to run the project, but when it comes to using the debugger from vscode it won't work
BRunning in debug mode is my goal
IYou also cross-posted this in #workerd, please don't do that in the future as I completely missed kian's responses/questions.
BYeah, sorry, just deleted my post there. Figure this would be a better channel.
BWhat do you mean here ?
Itsc outputs a Javascript file. But you can't run that Javascript file directly with Node.js, it's not compatible.IYou need to run Wrangler, which will then run the JS file for you.
BWhere are you seeing this ? I am running with wrangler (package.json)
II'm seeing in the Debug Console the line
<path>/bin/node ./out/index.js which makes it seem like you're running it directly with Node.II'm assuming the launch.json isn't properly configured?
IThat's the error you'd see if it was run directly with Node instead of Wrangler.
BYes, my intention is to set it up the right way, but I don't know how.
II don't have much experience with VSCode's launch.json either unfortunately, so I might not be able to help much here.
BNo a problem, thanks though
BHas anyone else had to configure VSCode to run in debug mode for a TS Node project that includes a Cloudflare Worker?
GMaybe I'm getting a little ahead of myself, but I'm poking around some experimental types and trying to make this new RPC thing work. Just spent the weekend trying to build a Durable Object Proxy thingy, so this is great timing 
. Looking forward to an announcement
https://github.com/cloudflare/workerd/blob/f04e5ce5a25df2f394dc420e330946ea3ea8e67e/types/test/types/rpc.ts
. Looking forward to an announcementhttps://github.com/cloudflare/workerd/blob/f04e5ce5a25df2f394dc420e330946ea3ea8e67e/types/test/types/rpc.ts
GitHub
The JavaScript / Wasm runtime that powers Cloudflare Workers - cloudflare/workerd
SIs there anyway to "hotfix" an environment variable's value after deployment? If so, what are the implications of pushing a change?
SUse case: authentication key for a 3rd party app changes, you don't want to have to redeploy
