You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For dev you can just use the CLI flag, e.g. wrangler dev pages --compatibility_date=... but for production wrangler.toml is being ignored--at least by wrangler. There's no way to test if the CF production run-time grabs and uses wrangler.toml and/or if wrangler.toml was error-free.
Please provide a link to a minimal reproduction
Just add a random wrangler.toml with a compatibility_date and run wrangler WITHOUT the flag.
Please provide any relevant error logs
No response
The text was updated successfully, but these errors were encountered:
Hey! 👋 Apologies for the delayed response. Right now, you'll need to configure your production compatibility date in the Cloudflare dashboard:
We're working on converging the Workers and Pages experiences which should allow this to be configured in a config file: https://blog.cloudflare.com/pages-and-workers-are-converging-into-one-experience/. This is still a ways out though, so you'll need to use the dashboard for now.
Which Cloudflare product(s) does this pertain to?
Pages
What version(s) of the tool(s) are you using?
3.5.0
What version of Node are you using?
18
What operating system are you using?
WSL
Describe the Bug
For dev you can just use the CLI flag, e.g.
wrangler dev pages --compatibility_date=...
but for productionwrangler.toml
is being ignored--at least bywrangler
. There's no way to test if the CF production run-time grabs and uses wrangler.toml and/or if wrangler.toml was error-free.Please provide a link to a minimal reproduction
Just add a random wrangler.toml with a compatibility_date and run wrangler WITHOUT the flag.
Please provide any relevant error logs
No response
The text was updated successfully, but these errors were encountered: