npx wrangler deploy --route '<custom path>/*' --name <dynamic name> but it's complaining that I didn't specify a zone ID or name
npx wrangler deploy --route '<custom path>/*' --name <dynamic name>
H<custom path> value contain a hostname? Like example.com/*? Or just a path?
GG
MMG
.env
all OK now
JJJJJ
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
KKFor Miniflare v3, we’re now using the industry-standard SQLite, with a separate blob store for KV values, R2 objects, and cached responses.
K
DC
.wrangler folder again i do see those SQLite and blobs, was just partly hoping there's still a way for a redis support. Thanks!MMJ
AP
E
npm create cloudflare@2 and when starting it it raises the warn/error:
C2023-05-18 it should remove that message. You can also just ignore itE
C
.pages.dev domain. The staff use it to check their logsWput: 'Value length of 39837727 exceeds limit of 26214400.'
WW<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].wranglernpm create cloudflare@2[mf:wrn] The latest compatibility date supported by the installed Cloudflare Workers Runtime is "2023-05-18",
but you've requested "2023-06-14". Falling back to "2023-05-18"...2023-05-18.pages.dev