H
wrangler.toml
J
H
wrangler versions is not working in 3.68, even though it's supposed to be there since a while.
Jmysite-stagingwrangler.toml<nameFromWrangler>-<nameSpecified> , or worker- if outside a dir containing wrangler.tomlwrangler.json
Anpm create cloudflare@2.21.1 auto-upgrading to the latest minor version? I understand that, in a lot of cases, it's completely safe to use the latest minor as it's non-breaking.2.21.1 where the initial list of options is a long-ish list - now it's been tidied up to be into categories with the lists behind. This means anywhere this command is used needs rewriting to account for the new options - not a large amount of work - but if this happens again it then means the printed material would come across wrong, which would be fixed by pinning the version, but it refuses to run without upgrading to the latest minor.A
npm create cloudflare@2.21.1 -- --no-auto-update (didn't realise this existed!)
Swrangler deploy isn't working as it did before (on the same workspace):
KSSbun run deploy
H
V
S
!
!!
wrangler 3.32.0 (update available 3.68.0)wrangler@3.68.0 to remove this warning.
B
1
Mwrangler dev has been acknowledged by anyone, or if someone is already on it: https://github.com/cloudflare/workers-sdk/issues/5918MyDurableObject#myMethod as Durable Object RPC is not yet suppor...
CC
HCH
CH
env.ASSETS
Iwrangler tail
O
WWCHH
D
M
Miniflareunstable_devMiniflareMiniflare
M
I
J
!
EJ
D
AHAH
wrangler versionsmysite-staging<nameFromWrangler>-<nameSpecified>worker-npm create cloudflare@2.21.12.21.1npm create cloudflare@2.21.1 -- --no-auto-updatewrangler deploy✘ [ERROR] Missing entry-point: The entry-point should be specified via the command line (e.g. `wrangler deploy path/to/script`) or the `main` config field.bun run deploywrangler@3.68.0wrangler devMyDurableObject#myMethodbunx wrangler d1 create mysite-staging
bunx wrangler r2 bucket create mysite-staging
bunx wrangler kv:namespace create staging