<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Promises on Nalar</title>
    <link>https://nalar.dev/tags/promises/</link>
    <description>Recent content in Promises on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 01 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/promises/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Choosing JavaScript Promise Combinators: all, allSettled, any, and race</title>
      <link>https://nalar.dev/promise-combinators-all-allsettled-any-race/</link>
      <pubDate>Tue, 01 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/promise-combinators-all-allsettled-any-race/</guid>
      <description>&lt;p&gt;JavaScript provides several Promise combinators that look similar but encode very different failure policies. Choosing between &lt;code&gt;Promise.all&lt;/code&gt;, &lt;code&gt;Promise.allSettled&lt;/code&gt;, &lt;code&gt;Promise.any&lt;/code&gt;, and &lt;code&gt;Promise.race&lt;/code&gt; is less about syntax and more about defining what &amp;ldquo;success&amp;rdquo; means for a group of asynchronous operations.&lt;/p&gt;&#xA;&lt;p&gt;The important question is not &amp;ldquo;which one runs in parallel?&amp;rdquo; Promises usually start when you create them. The combinator decides how to observe their outcomes.&lt;/p&gt;&#xA;&lt;h2 id=&#34;promiseall-every-result-is-required&#34;&gt;&lt;code&gt;Promise.all&lt;/code&gt;: every result is required&lt;/h2&gt;&#xA;&lt;p&gt;Use &lt;code&gt;Promise.all&lt;/code&gt; when the operation is successful only if every input fulfills.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
