This repository has been archived by the owner on Aug 3, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 337
[dev] return granular API error messages #1330
Comments
As for the API error messages, we should definitely make those show up when running |
Good catch! Updated to: Got a new error when using a bad KV Namespace:
I think it would be good to add the actual error returned from the API for this command. |
ok - this is great info! thanks @jahands 😄 |
EverlastingBugstopper
changed the title
Wrangler Dev requires Cloudflare API
[dev] return granular API error messages
May 27, 2020
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
🐛 Bug Report
Wrangler Dev command won't work if Cloudflare API is down, is there a technical reason to require something from the Cloudflare API for testing locally?
Environment
WSL1 on Windows 10
rustc -V
:Not installed
node -v
:v8.10.0
wrangler -V
:wrangler 1.9.0-rc.1
wrangler.toml
Steps to reproduce
Run
wrangler dev
when the API is downWhat did you expect to see?
Local environment running worker
What did you see instead?
Error: Could not upload your script. Check your internet connection or https://www.cloudflarestatus.com/ for rare incidents impacting the Cloudflare Workers API.
The text was updated successfully, but these errors were encountered: