</>PackageGraphPackageGraph

p-map

npmv7.0.7TypeScript

Map over promises concurrently

Safe to adopt

Yes — p-map scores well across adoption, maintenance, weight, supply chain, and licensing. No download data reported for this package yet. Last published 13 days ago. 5 releases in the last 2 years.

  • ?Adoption: grade ?, Not reported by this registry.

    No download data reported for this package yet.

  • AMaintenance: grade A, Excellent.

    Last published 13 days ago. 5 releases in the last 2 years.

  • AWeight: grade A, Excellent.

    Zero runtime dependencies, about 21 KB installed.

  • BSupply chain: grade B, Good.

    This package has a single maintainer (bus factor of 1).

  • ALicense: grade A, Excellent.

    MIT — permissive, with no copyleft found in the dependency tree.

Grades are computed deterministically from registry metadata collected by PackageGraph — downloads, dependents, publish dates, the resolved dependency tree, maintainer count, and declared licenses. No third-party scores are used.

Install cost

What you actually take on by adding p-map to a project.

0
Direct dependencies

Runtime packages this one declares itself.

0
Total installed

Distinct packages in the full runtime tree, deduplicated the way a package manager would.

21 KB
Install size

Unpacked size of this package plus its entire runtime tree.

—
Tree depth

Longest resolved dependency chain below this package.

Compatibility

Node.js
node >=18
Module format
ESM only
TypeScript
Types included
Install scripts
None

Quick start

A usage example from the p-map README.

jsFull README ↗
import pMap from 'p-map';
import got from 'got';

const sites = [
	getWebsiteFromUsername('sindresorhus'), //=> Promise
	'https://avajs.dev',
	'https://github.com'
];

const mapper = async site => {
	const {requestUrl} = await got.head(site);
	return requestUrl;
};
Example truncated — see the full README.

p-map vs the alternatives

Packages solving a similar problem in the npm ecosystem, compared on the signals that drive an adoption decision.

PackageWeekly downloadsDependentsLicenseLast release
p-mapthis page01MIT13 days ago
p-locate216.9M1MIT1 day ago
p-limit293.1M5MIT1 day ago
cross-fetch32.9M2MIT1 day ago
await-lock01MIT1 day ago
es-get-iterator01MIT1 day ago

Dependencies

Declared by p-map v7.0.7. Runtime dependencies are installed with the package; dev dependencies are not.

Dev (8)

ava ^5.2.0chalk ^5.3.0delay ^6.0.0in-range ^3.0.0random-int ^3.0.0time-span ^5.1.0tsd ^0.29.0xo ^0.56.0

Used by

Popular packages that depend on p-map.

cacachenpm

Fast, fault-tolerant, cross-platform, disk-based, data-agnostic, content-addressable cache.

↓ 0/wk◈ 1 dependents⚖ ISC

Relationship graph

Dependencies (left) and dependents (right) of p-map.

cacachep-map
p-map dependencies dependents

Frequently installed together

minipass-pipelinenpm

create a pipeline of streams using Minipass

↓ 23.5M/wk◈ 2 dependents⚖ BlueOak-1.0.0TS
globnpm

the most correct and second fastest glob implementation in JavaScript

↓ 0/wk◈ 35 dependents⚖ BlueOak-1.0.0TS
ssrinpm

Standard Subresource Integrity library -- parses, serializes, generates, and verifies integrity metadata according to the SRI spec.

↓ 0/wk◈ 2 dependents⚖ ISC
@npmcli/fsnpm

filesystem utilities for the npm cli

↓ 0/wk◈ 1 dependents⚖ ISC
fs-minipassnpm

fs read and write streams based on minipass

↓ 0/wk◈ 1 dependents⚖ ISC
minipass-collectnpm

A Minipass stream that collects all the data into a single chunk

↓ 0/wk◈ 1 dependents⚖ ISC

Release history

5 releases in the last two years, typically about 196 days apart.

Recent versions of p-map
VersionPublishedSizeLicense
7.0.7latest13 days ago21 KBMIT
7.0.61 month ago21 KBMIT
7.0.52 months ago21 KBMIT
7.0.410 months ago21 KBMIT
7.0.31 year ago21 KBMIT
7.0.22 years ago20 KBMIT
7.0.12 years ago20 KBMIT
7.0.02 years ago20 KBMIT
6.0.03 years ago16 KBMIT
5.5.04 years ago16 KBMIT
5.4.04 years ago16 KBMIT
5.3.04 years ago14 KBMIT
5.2.04 years ago14 KBMIT
5.1.05 years ago10 KBMIT
5.0.05 years ago8.5 KBMIT

Overview

p-map is an npm package that map over promises concurrently. It has 1 known dependents in the graph. The latest version is 7.0.7, released under the MIT license.

Who should use it

Teams working in the npm ecosystem who need map over promises concurrently and value a focused solution.

When not to use it

Consider an alternative if you need to or if a more actively-maintained option better fits your npm stack.

Pros

  • Ships TypeScript type definitions.
  • Clear open-source license (MIT).

Cons

  • No significant drawbacks detected from available metadata.

Auto-generated from collected registry metadata. No external claims are inferred.

Maintainers

sindresorhus

Keywords

asyncawaitbluebirdcollectionconcurrencyconcurrentlyfulfillediterableiteratormapparallelpromisepromisesraceresolvedwait

Funding

Frequently asked questions

Should I use p-map?

Yes — p-map scores well across adoption, maintenance, weight, supply chain, and licensing. No download data reported for this package yet. Last published 13 days ago. 5 releases in the last 2 years.

How do I install p-map?

Run `npm install p-map` to add p-map to your npm project.

What license is p-map released under?

p-map is distributed under the MIT license.

How popular is p-map?

npm does not publish download counts. Within PackageGraph's crawl, 1 known packages depend on p-map.

Is p-map still maintained?

The most recent release of p-map (v7.0.7) was published 13 days ago.

Does p-map run install scripts?

No. p-map does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.