Bump p-map from 4.0.0 to 6.0.0

[dependabot]

Bumps p-map from 4.0.0 to 6.0.0.

Release notes

Sourced from p-map's releases.

v6.0.0

Breaking

• Require Node.js 16 (#65) df88787
• Switch from aggregate-error package to the native AggregateError
  • This only affects you if you use {stopOnError: false}.
  • The native one is similar, but differs in error message: sindresorhus/aggregate-error#4

sindresorhus/p-map@v5.5.0...v6.0.0

v5.5.0

• Add pMapSkip as an acceptable return value in Mapper type (#60) b58fc26

sindresorhus/p-map@v5.4.0...v5.5.0

v5.4.0

• Support AbortController (#58) 4875dee

sindresorhus/p-map@v5.3.0...v5.4.0

v5.3.0

• Add support for multiple pMapSkip's (#52) 94eb532

sindresorhus/p-map@v5.2.0...v5.3.0

v5.2.0

• Add support for AsyncIterable as input (#46) a24e909
• Prevent some potential unhandled exceptions (#48) 11bc75d

sindresorhus/p-map@v5.1.0...v5.2.0

v5.1.0

Improvements

• Add the ability to skip an iteration (#39) c9c0882

Fixes

• Do not run mapping after stop-on-error happened (#40) 4b5f9e7

sindresorhus/p-map@v5.0.0...v5.1.0

v5.0.0

Breaking

• Require Node.js 12 dcdbc7a
• This package is now pure ESM. Please read this.
• AggregateError is no longer iterable. It moved to an .errors property.

sindresorhus/p-map@v4.0.0...v5.0.0

Commits

• 66b039b 6.0.0
• ebb7c70 Meta tweaks
• df88787 Drop aggregate-error dependency and require Node.js 16 (#65)
• a5faf42 5.5.0
• b58fc26 Add pMapSkip as an acceptable return value in Mapper type (#60)
• 5ef93c2 5.4.0
• 4875dee Support AbortController (#58)
• 735d80e Add another test
• 3b62341 5.3.0
• 94eb532 Add support for multiple pMapSkip's (#52)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[adaptly-bot-dev]

ℹ️  Breaking Changes in the Dependency's Changelog. Check breaking changes and run /adaptly go to continue checking next versions.

Package: p-map
Version: v5.0.0

 Breaking changes

1: Require Node.js 12

The package now requires Node.js 12 or higher.

2: Package is now pure ESM

The package is now pure ECMAScript Modules (ESM). Please refer to the provided link for more information.

3: AggregateError is no longer iterable

The AggregateError object is no longer iterable. It has been moved to an .errors property.

1 / 7 versions between v4.0.0 and v6.0.0 checked

[adaptly-bot-dev]

ℹ️  Breaking Changes in the Dependency's Changelog. Check breaking changes and run /adaptly go to continue checking next versions.

Package: p-map
Version: v6.0.0

 Breaking changes

1: Require Node.js 16

The package now requires Node.js 16. Make sure to update your Node.js version if you are using this package.

2: Switch from aggregate-error package to the native AggregateError

If you use {stopOnError: false}, this change affects you. The package now uses the native AggregateError instead of the aggregate-error package. The error message may differ. Make sure to update your code accordingly.

7 / 7 versions between v4.0.0 and v6.0.0 checked

[adaptly-bot-dev]

⚠️  p-map@v5.0.0

 Breaking changes

1: Require Node.js 12

The package now requires Node.js 12 or higher.

2: Package is now pure ESM

The package is now pure ECMAScript Modules (ESM). Please refer to the provided link for more information.

3: AggregateError is no longer iterable

The AggregateError object is no longer iterable. It has been moved to an .errors property.

[adaptly-bot-dev]

⚠️  p-map@v6.0.0

 Breaking changes

1: Require Node.js 16

The package now requires Node.js 16. Make sure to update your Node.js version if you are using this package.

2: Switch from aggregate-error package to the native AggregateError

The package now uses the native AggregateError instead of the aggregate-error package. This change only affects you if you use {stopOnError: false}. The native AggregateError is similar to the previous package but differs in error message. Make sure to update your code if you rely on the error message from the aggregate-error package.

[adaptly-bot-dev]

⚠️  p-map@v5.0.0

 Breaking changes

1: Require Node.js 12

The package now requires Node.js version 12. Update your Node.js version if it's older to avoid compatibility issues.

2: Package is now pure ESM

The package has transitioned to pure ECMAScript Modules (ESM). Ensure your application supports ESM to avoid import/export issues.

3: AggregateError is no longer iterable

AggregateError has been updated and is no longer iterable. It now uses an .errors property. Update your code to iterate over aggregateError.errors instead of aggregateError.

- for (const error of aggregateError) {...}
+ for (const error of aggregateError.errors) {...}

[adaptly-bot-dev]

⚠️  p-map@v6.0.0

 Breaking changes

1: Require Node.js 16 (#65)

The package now requires Node.js 16. If you are using an older version of Node.js, you will need to upgrade to continue using this package.

2: Switch from aggregate-error package to the native AggregateError

The package has switched from using the aggregate-error package to the native AggregateError. This only affects you if you use {stopOnError: false}. The native one is similar, but differs in error message. You may need to adjust your error handling code accordingly.