npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

p-some-first

v1.1.0

Published

Returns the first Promise in an iterable to resolve

Downloads

3

Readme

p-some-first

Like Promise.all/Promise.any but only returns the first resolved value.

import PCancelable from "p-cancelable";
import pSomeFirst from "p-some-first";

(async () => {
	await pSomeFirst([
		new PCancelable((resolve) => setTimeout(() => resolve(1), 1000)),
		new PCancelable((resolve) => resolve(2)),
	]);
	// resolves to 1

	await pSomeFirst([
		new PCancelable((resolve, reject) => reject("error message")),
		new PCancelable((resolve, reject) => reject(new Error("intentional"))),
		new PCancelable((resolve, reject) => reject(42)),
	]);
	// rejects with ["error message", new Error("intentional"), 42]

	await pSomeFirst(
		[
			new PCancelable((resolve, reject) => reject("error message")),
			new PCancelable((resolve, reject) =>
				reject(new Error("intentional"))
			),
			new PCancelable((resolve, reject) => reject(42)),
		],
		7
	);
	// resolves to the fallback value (7)
})();

See the tests for more examples.

Cancelable Promises SHOULD be used otherwise there is hardly any difference between using p-some-first and this:

Promise.allSettled([
	Promise.reject(new Error("something")),
	Promise.resolve(42),
]).then((rr) => {
	return rr.find((r) => r.status === "fulfilled").value;
});

By using cancelable Promises, after one Promise resolves, all remaining Promises can be canceled and pSomeFirst will return without waiting for all promises to settle. Cancelable Promises will also help to minimize any errant UnhandledPromiseRejectionWarnings. Until JavaScript gets a way to cancel native Promises, you can use a library like p-cancelable or Bluebird to create cancelable Promises.

If cancelable Promises are not used (in a Node.js environment), a process warning will be emitted notifying you about this.