🚀 Feature Request: Print details of issues

[frontendphil]

Describe the solution

When a worker doesn't deploy, the error messages I've seen so far aren't helping me at all to fix the problem.

See, for instance, the screenshot below:

Ok, I've reached some limits. However, this doesn't answer any of the following questions:

• What is the limit?
• How long did my code run? (Maybe you can run it to completion and then enforce stuff? I don't know.)
• Can I adjust the limit? And if so, where can I do that?

I had very similar issues when my server bundle got too large. I only got informed that it was too large, but the error didn't tell me how large it was exactly, what the limit was, and how I could fix it. I had to figure out that $5 more a month did the trick, and I happily paid that. However, being stuck at this error for 2hrs didn't make me happy.

---

A very similar issue are the "You need to also update this in your wrangler.toml file messages. These are great if they would tell me exactly which key I need to set. Context: After I've increased the CPU limit in the settings, they are gone with a new deployment because, apparently, they aren't in my wrangler.toml. It would be just great if the same dialog that lets me configure something in the UI would also tell me what to put into my wrangler.toml.