Question 1

What does this error message mean and how do I fix it?

Accepted Answer

Paste the error message or full stack trace into errlens. It matches the text against a library of common errors and shows, in plain English, what the message means, the most likely causes, and concrete steps to fix it — plus the language or runtime it came from. If it can't find an exact match, it gives clearly-labelled general guidance instead of guessing.

Question 2

Which languages and runtimes does errlens cover?

Accepted Answer

It covers common errors in JavaScript and TypeScript (Node and the browser), Python, Java, Go, Rust, Bash and shell, HTTP status codes such as 401, 404, 429 and 500, plus frequent npm and git errors. The library focuses on the errors developers hit most often rather than every possible message.

Question 3

Is the error text I paste sent anywhere?

Accepted Answer

No. errlens runs entirely in your browser and a strict Content-Security-Policy sets connect-src to none, so the page cannot make any network request even if it tried. Nothing you paste — error text, stack traces, file paths — ever leaves your device.

Question 4

What happens if my error isn't in the library?

Accepted Answer

errlens degrades gracefully. It looks for well-known signal words such as timeout, out of memory, or connection reset and offers honest, clearly-labelled general guidance. If even that doesn't apply, it points you to practical next steps: search the exact error type with your language, read the top of the stack trace, and reproduce with the smallest failing input.

Question 5

Can errlens read a full stack trace, not just one line?

Accepted Answer

Yes. Paste the whole trace. errlens extracts the error type from the top and the first location frame, and uses the full text to rank matches, so a distinctive line deep in the trace still helps identify the problem.

Paste the error. Get what it means and how to fix it.

Your error

Diagnosis