#error-handling

JMJessica Malljessicaspeaks.hashnode.dev

Quick Fixes for the 5 Most Common Node.js Errors

Node.js apps often hit a few recurring runtime errors that are easy to diagnose once you know the usual causes. The following quick guide explains five common errors, why they happen, and simple fixes

14h ago2 min read

TTechinpowerplatformdev.hashnode.dev

Power Fx Error Handling Explained (Error, IfError, IsError, IsBlankOrError)

When building applications using Microsoft Power Apps, errors are inevitable. They can occur due to invalid user input, network failures, permission issues, or incorrect formulas. To build reliable ap

4d ago4 min read

CVChris Vesterscvesters.hashnode.dev

API Error Messages

When designing an API, we tend to only focus on successful requests. This often leads to error responses that are not useful and often don't contain any information. I am guilty of this myself, and in my own projects I typically only use the HTTP sta...

4d ago6 min read

MAMohammad Almechkorhex-di.hashnode.dev

Stop Throwing, Start Returning: Why TypeScript Needs the Result Pattern

You've written this code a hundred times: try { const user = await fetchUser(id); const posts = await fetchPosts(user.id); const rendered = renderProfile(user, posts); return rendered; } catch

5d ago10 min read

AVAravind Viswanathanaravindv.pro

When Consumers Fail: Extending Selective Retry to Kafka

Designing a Kafka Error Pipeline Kafka consumers fail for the same reason every distributed component fails: not all errors mean the same thing. A network timeout, a malformed payload, and a downstrea

Mar 47 min read

DGDevTools Guidedevtoolsguide.hashnode.dev

Effect-TS: Building Robust TypeScript Applications with Typed Effects

Effect-TS: Building Robust TypeScript Applications with Typed Effects Effect-TS is a TypeScript framework that brings the power of effect systems to JavaScript/TypeScript applications. If you've struggled with error handling, dependency injection, or...

Mar 36 min read

SMSarkis Mrailway-ts-pipelines.hashnode.dev

Typed Errors in TypeScript: The Options, the Tradeoffs, and the Missing Middle

When a function throws, the error channel disappears from the type system. The caller gets unknown in a catch block. There's no equivalent to Java's throws clause. No way for the compiler to say: Thi

Mar 18 min read

PJPriyanshu Jajalasync-js-explained.hashnode.dev

Async JavaScript Explained — Part 2

Welcome back! In Part 1, we covered callbacks, callback hell, and the basics of Promises. Now we'll dive deeper into advanced Promise techniques and modern async/await syntax that will transform how y

Feb 2312 min read

STShailaja Tripathireact-mastery-series.hashnode.dev

📘 React Mastery Series — Day 24

Error Boundaries in React — Handle UI Crashes Gracefully In real applications, things can go wrong: API fails Component crashes Unexpected undefined values Runtime errors By default, if a compon

Feb 233 min read

VHVitali Haradkouvitalicset.hashnode.dev

Option<T> and Result<T, E> in TypeScript: The Missing Error Handling Primitives

TypeScript's type system is excellent at modeling data shapes. It's much weaker at modeling control flow — specifically, the two most common sources of bugs in any codebase: absent values and failed o

Feb 204 min read

Tag feed

Tag feed

#error-handling

Quick Fixes for the 5 Most Common Node.js Errors