H
JJH
K
export default) don't have bindings as globals, it's under env
Jwrangler devworkerd--remote runs your code on a remote Cloudflare controlled server, so it's a bit slower, but you avoid the need for local workerdwrangler@2 for now, which uses a more simulated local environment with node.js
Gnpx wrangler deploy (without -e)?
HGG
npx wrangler deploy --route '<custom path>/*' --name <dynamic name> but it's complaining that I didn't specify a zone ID or nameH<custom path> value contain a hostname? Like example.com/*? Or just a path?GG
MMG.env
all OK nowJJJJJ
WWWW
WW
G
kj warnings are from workerd.G
Home to Wrangler, the CLI for Cloudflare WorkersĀ® - workers-sdk/handler.ts at 05099f4c9ff1f57d62db5b73a8aea73d1ab1aac6 Ā· cloudflare/workers-sdk
GGG
P
Cminiflare@3/wrangler@3? I am able to get it to work on miniflare@2, however when migrating to wrangler@3, wrangler dev[miniflare] section in the wrangler.toml
export default--remotewrangler@2npx wrangler deploy-enpx wrangler deploy --route '<custom path>/*' --name <dynamic name><custom path>example.com/*Error: write EOF
at WriteWrap.onWriteComplete [as oncomplete] (node:internal/stream_base_commons:94:16)
Emitted 'error' event on Socket instance at:
at emitErrorNT (node:internal/streams/destroy:151:8)
at emitErrorCloseNT (node:internal/streams/destroy:116:3)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
errno: -4095,
code: 'EOF',
syscall: 'write'
}kjminiflare@3wrangler@3wrangler@3miniflare@2[miniflare]export default {
async fetch(req, env, ctx) {
// ...
console.log(env.TOKEN);
// ...
}
}