wrangler deployments list or wrangler deployments view [deployment-id] also gave you the URL to the worker. Just like it does when we use wrangler deploy
wrangler deployments listwrangler deployments view [deployment-id]
C
N
J
M
npm init --from-dash converting worker.js into src/index.ts?C
R
B
wrangler.tomldeploy --dry-run --outdir dist, the generated code shows the variable replaced. However, when I run devReferenceError: __IS_DEPLOYED_BUILD__ is not defined. What may be adding weirdness here is that __IS_DEPLOYED_BUILD__ is in a transitive dependency. Not sure how to view the generated code that dev--outdir...
K$TMPDIR, along the lines of tmp-55872-3xWssSNdPdH6/index.js.Kvar src_default then you'll find it pretty easily.B__IS_DEPLOYED_BUILD__ either....BKindex.js.map - but no idea on the missing __IS_DEPLOYED_BUILD__ part.KKBBK
if (__IS_DEPLOYED_BUILD__), although that depends if you already have sourcemaps because otherwise it probably makes debugging horrible.K
Bunstable_dev?
J
S
Cenvironment for a service binding e.g. production, stagingdevstage, it doesn't find the related stage version of the service, which exists. The only way to get it to work is to remove the environment in the binding in the wrangler.toml, and then append "stage" to my service name. Is this expected? I presume it doesnt "find" the service because the service name is deployed as <service>-<environment> which is why the second code example works. 
Kenvironment is for old Service Environments which haven't been around for awhileK[env.foo]) are purely Wrangler abstractions and as you've seen, are actually separate Workers with different names.C
A
E
Tvite build --watch my first terminal and wrangler pages dev .svelte-kit/cloudflare --live-reload in my second terminal. 
S
I am facing an issue when I am using middlewares in Pages. They are not invoked when there's a double slash in the URL. I have described the issue in more detail in #functions channel. Can anybody help me with this? 
Z
JC
M
wrangler dev, is the dev.host config property (and the rest of request forwarding) only respected in --remote mode? Digging through the wrangler source, that seems to be the case, and wrangler is returning 404 without even trying the upstream server specified in the configMC
HHCCCCCK
node-gyp issueKCnpm init --from-dash[define]
__IS_DEPLOYED_BUILD__ = "true"deploy --dry-run --outdir distReferenceError: __IS_DEPLOYED_BUILD__ is not defined__IS_DEPLOYED_BUILD____IS_DEPLOYED_BUILD____IS_DEPLOYED_BUILD__--outdir$TMPDIRtmp-55872-3xWssSNdPdH6/index.jsvar src_defaultindex.js.mapif (__IS_DEPLOYED_BUILD__)unstable_dev--kv KV_STORE=d4dd19ae...environmentenvironmentenvironmentproductionstagestage<service>-<environment>services = [
{ binding = "auth", service = "auth", environment = "stage" }
]services = [
{ binding = "auth", service = "auth-stage" }
][env.foo]vite build --watchwrangler pages dev .svelte-kit/cloudflare --live-reloadwrangler devdev.host--remotenode-gyp