In development, it's easy to break Eleventy without noticing. In a lot of other tools, there's often some type of "error overlay" that pipes build errors directly to the browser. This is that, for Eleventy.
Like .tap, but for errors (rejections)
Named API errors with original status code and custom message.
An High Intelligence Module recognize errors for you
Shared types, errors, and utilities for wallet-abstractor
create a bunch of custom errors
<a name="Errors"></a> ## Errors : <code>object</code> # Custom and Explicit Javascript Error Classes
GraphQL server extension to track requests with errors
Browser SDK for Loomtraze — sessions, errors, network signals, and more.
Centinela library to gestionate errors
Print full API responses in your Mocha tests when you get an unexpected responses.
Forces TypeScript to ignore `node_modules`. Preventing VSCode from showing errors in the problems view from files in `node_modules`.
Lightweight developer notification tool for OTPs, errors, and events in local development.
This fixes the problem where console.log errors out
Emit errors described by a code and context.
A simple middleware for handling HTTP errors
Package to maintain errors
Trace errors and store error metrics in the cloud.
This is a set of API errors written in Nest.js used by the organization ruden.pro.
Render Zod errors in Monaco Editor (the editor used by VSCode).
No description provided.
Human-readable Zod errors. Turn invalid_string + email at path 'age' into 'Age is not a valid email address' — with full customisation and a React hook.
console logs, errors, debug, info and warning on the screen
Send errors to slack