Weird. It has worked locally for the past few days, so I'm wondering what broke it now...
Weird. It has worked locally for the past few days, so I'm wondering what broke it now...
v18.7.0. Is that the issue?v18.3.0.Volta, but I didn't know you could pin for specific projects. Thanks!production tag underneath their name, and the listing also mentions 1 environment. I can also see some info when I click Manage service in the workers' overview. wrangler.toml and then deploy them using --env, wrangler deploys separate services with the env name from the wrangler.toml as a suffix to the name. Kinda defeats the whole purpose of mentioning environments in the dashboard in the first place.
production relates to Service Environments https://developers.cloudflare.com/workers/learning/using-services/#service-environments which has been temporarily disabled while they work on the feature
npx wrangler pages dev dist --r2=BUCKET
miniflare section. Unless you are using MiniflareScope (Access)
- account (read)
- user (read)
- workers (write)
- workers_kv (write)
- workers_routes (write)
- workers_scripts (write)
- workers_tail (read)
- pages (write)
- zone (read)
- offline_accessWhile developing locally, you can interact with an R2 bucket by adding --r2=<BINDING> to your run command. For example, if your bucket is bound to BUCKET, you can access this bucket in local dev by running npx wrangler pages dev dist --r2=BUCKET.v18.7.0v18.3.0