it doesnt really matter where its actually "running"
it doesnt really matter where its actually "running"
Abut also it seems like that workers.dev url is not actually accessible so I guess its an internal URL?
Aactually i guess in a proxying scenario with something like nginx would the destination webserver see the original request origin
Aor does it show up on a header somewhere
Adifferent question: is there a way to have a custom build in wrangler 2 that also supports live-reloading?
Ajust using a custom webpack config, with wrangler 1 it would just autoreload automatically
Ayeah i saw this, but it doesn't appear to be working for me. It says the watch_dir defaults to the current working directory, does that mean I don't need to set it at all if that default is appropriate? or is it referring to the "cwd" setting, which I'd then need to set
Ai tried with neither of them set, and with both of them set to
'./'Ait doesnt seem to no
Ait doesnt seem to work even if i provide the absolute path to the folder
A
Athis and then a bunch of other envs listed later on with more env vars
Aand routes
KI don’t think it’s a requirement - allowed, but not required.
The docs use it in one place and then don’t in another - there’s no real structure to it since there’s nothing strict in the TOML spec
The docs use it in one place and then don’t in another - there’s no real structure to it since there’s nothing strict in the TOML spec
Ayeah the indenting doesnt matter
Ajust to clarify whats supposed to happen is if I change any file in the directory it should trigger a new run of my custom build command, then restart the miniflare server right
Ayeah we have a somewhat complicated build setup thats pulling in shared packages from our monorepo and doing some other stuff
A2.0.23
Athats actually the mode im using
Ai see
Amade one here https://github.com/cloudflare/wrangler2/issues/1566
GitHub
What version of Wrangler are you using? 2.0.23 What operating system are you using? Mac Describe the Bug I have a wrangler.toml file that looks like the following name = "js" acco...
S
I just noticed wrangler uses react
JThe way wrangler uses react is so interesting to me honestly - and one of the few reasons I’ve got more familiar with react recently haha. I’d love to read some more about the design decisions there in a post or something though I’m not sure it has mainstream appeal 
JOh very interesting 
WWell (not speaking for the wrangler team), Wrangler I think will always stay react but will be exposing APIs for others to build on top of.
So you could build a Vue version if you wanted or just build your own tooling and have Wrangler power that (much easier to maintain)
So you could build a Vue version if you wanted or just build your own tooling and have Wrangler power that (much easier to maintain)
Jvery cool
CIs it possible for wrangler to set a none secret environment value? Using GitHub action and I add the git hash as a secret and it seems silly to.
JHey everyone got another fun thing in the pipeline (I am sure R2 objects is interesting and all) how about https://github.com/cloudflare/wrangler2/issues/1583
GitHub
Why should we do wrangler init --from-dash? Furthering the discussion from #1346, we want to provide a bridge from the dashboard where previously it was easy to get up and going with a new Worker. ...
JNo. I suppose you could dump the stdout into a text file if you wanted or if your terminal keep output logs it would be there
CHas anyone run into a 522 when running
wrangler devHope ya'll enjoyed the Office Hours
