Error Message Explainer

In short A stack trace is read from the top for what went wrong and from the bottom for where it started. The first line names the exception type and the message; the frames below it show the call path, with the code closest to the failure at the top and your own entry point at the bottom. The most useful line is usually the topmost frame that belongs to your code rather than a library, because that is where your assumption and the library's expectation diverged. Most errors fall into a few families that are worth recognising by shape. A null or undefined reference means something you expected to exist did not — usually because a lookup returned nothing and was not checked. A type error means a value was a different shape than assumed, and in JavaScript that is frequently an API returning an object where an array was expected. A module-not-found is an install or a path problem, not a code problem. And a permission or connection refused is environment rather than logic. Reading the message literally is the underrated skill: it usually says exactly what happened.