Promise.try in JavaScript: One Error Path for Sync and Async

Stop mixing try/catch with Promise chains - JavaScript's new Promise.try handles return values, Promises, and errors uniformly

Trevor I. Lasn Trevor I. Lasn
Updated 3 min read

JavaScript now has a Promise utility that makes handling potentially async functions cleaner and safer. Promise.try lets you wrap any function in a Promise, whether it’s async or not, while maintaining optimal execution timing.

The Core Problem

Handling functions that might be sync or async requires mixing different error handling patterns:

JavaScript
function getUserData(id) {
// We need try/catch for sync errors
try {
validateId(id);
// Might return cached data synchronously
if (id in cache) {
return cache[id];
}
// Might return a Promise
return fetch(`/api/users/${id}`);
} catch (syncError) {
handleSyncError(syncError);
}
}

The problem? You never know which behavior you’ll get. Currently, there are two common ways to handle this, but neither is ideal:

JavaScript
// Method 1: Using Promise.resolve().then()
Promise.resolve().then(() => getUserData(123));
// ❌ Forces everything to be async
// ❌ Even cached data waits for the next tick
// ✓ But at least it catches errors
// Method 2: Using new Promise
new Promise(resolve => resolve(getUserData(123)));
// ❌ Verbose and clunky
// ❌ Easy to get wrong
// ✓ Runs sync code immediately

We need a better way to:

  • Run synchronous code immediately (for better performance)
  • Handle asynchronous code when needed
  • Catch any errors that might occur
  • Do all this with clean, readable syntax

The Solution: Promise.try

Promise.try gives us one clean way to handle all cases:

JavaScript
// Clean, safe, and optimal timing
Promise.try(() => getUserData(123))
.then(user => {
// Gets called with:
// - Immediate values (from cache)
// - Resolved Promise values (from fetch)
})
.catch(error => {
// Catches both:
// - Synchronous throws
// - Promise rejections
});

Why It’s Better

Promise.try has three key advantages:

JavaScript
// 1. Runs synchronously when possible
Promise.try(() => "instant") // Executes immediately
.then(x => console.log(x));
// 2. Catches all errors reliably
Promise.try(() => {
throw new Error('boom');
})
.catch(err => console.log('Caught:', err));
// 3. Handles both sync and async naturally
Promise.try(() => {
if (Math.random() > 0.5) {
return "sync value";
}
return fetch('/api/data');
});

Promise.try runs synchronous code immediately for better performance, while still handling async operations when needed. It catches every type of error through a single catch handler, and does it all with clean, readable syntax. Think of it as the Promise equivalent of a try-catch block - a safe way to execute code that might fail or might be async, without having to know which it is ahead of time.

This is particularly powerful when working with functions that might change their behavior over time. Your error handling remains consistent whether the function returns immediately or needs to make an API call. No more wrapping everything in try-catch blocks and then also handling Promise rejections separately.

References


Trevor I. Lasn

Trevor I. Lasn

Building whiteheap.com and 0xinsider.com.



Related Articles

Check out these related articles that might be useful for you. They cover similar topics and provide additional insights.

JavaScript
4 min read

Stop writing manual duration formatting code. Instead, leverage the new powerful Intl.DurationFormat API for internationalized time displays

Mar 13, 2025
Read article
JavaScript
9 min read

Deep dive into JavaScript Symbols - what they are, why they matter, and how to use them effectively

Nov 15, 2024
Read article
JavaScript
4 min read

Why the new Error.isError() method solves important cross-realm issues and provides more reliable error identification than instanceof

May 9, 2025
Read article
JavaScript
7 min read

A WeakRef points to an object without stopping the garbage collector from freeing it. When that helps, how deref() works, and cleanup with FinalizationRegistry.

Jan 7, 2025
Read article
JavaScript
5 min read

The Stage 2 pipeline operator passes a value through a chain of calls left to right, with % marking where it goes, instead of nesting h(g(f(x))).

Oct 29, 2024
Read article
JavaScript
8 min read

How to handle unique values and key-value pairs properly without type coercion and performance issues

Nov 17, 2024
Read article
JavaScript
7 min read

AggregateError holds several errors in one, the way Promise.any() reports that every promise rejected. How to throw and read it, plus the new SuppressedError.

Sep 2, 2024
Read article
JavaScript
4 min read

The 'with' statement is the only feature ever deprecated in JavaScript

Aug 22, 2024
Read article
JavaScript
4 min read

Understanding the new import attributes syntax and why we can't rely on file extensions alone

Nov 10, 2024
Read article

This article was originally published on https://www.trevorlasn.com/blog/promise-try-in-javascript. It was written by a human and polished using grammar tools for clarity.