es-shims/array.prototype.flatmap

An ESnext spec-compliant `Array.prototype.flatMap` shim/polyfill/replacement that works as far down as ES3.

es-shims

Everything required to ensure that a browser is as ECMAScript-compliant as possible. Require this, and everything will be as standard as it can be.

Tests

Simply clone the repo, npm install, and run npm test

array.prototype.flatmap's Issues

Dependency Dashboard

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Pending Approval

These branches will be created by Renovate only once you click their checkbox below.

• [Deps] Update Update eslint to v8.57.0
• [Deps] Update Update nyc to v15
• 🔐 Create all pending approval PRs at once 🔐

Detected dependencies

github-actions

.github/workflows/node-aught.yml

.github/workflows/node-pretest.yml

.github/workflows/node-tens.yml

.github/workflows/rebase.yml

.github/workflows/require-allow-edits.yml

npm

package.json

• call-bind ^1.0.5
• define-properties ^1.2.1
• es-abstract ^1.22.3
• es-shim-unscopables ^1.0.2
• @es-shims/api ^2.4.2
• @ljharb/eslint-config ^21.1.0
• aud ^2.0.4
• auto-changelog ^2.4.0
• eslint =8.8.0
• evalmd ^0.0.19
• for-each ^0.3.3
• has-strict-mode ^1.0.1
• in-publish ^2.0.1
• npmignore ^0.3.1
• nyc ^10.3.2
• object-inspect ^1.13.1
• safe-publish-latest ^2.0.0
• tape ^5.7.4
• node >= 0.4

---

• Check this box to trigger a request for Renovate to run again on this repository

An in-range update of @ljharb/eslint-config is breaking the build 🚨

The devDependency @ljharb/eslint-config was updated from 15.0.1 to 15.0.2.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@ljharb/eslint-config is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ Travis CI - Branch: The build canceled.

---

Commits

The new version differs by 4 commits.

• ac727d1 v15.0.2
• f10f0ad [Dev Deps] update safe-publish-latest
• aa8ef9f [actions] add automatic rebasing / merge commit blocking
• 323eeda [patch] disable prefer-regex-literals in tests

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

Extra item in resulting Array

Hi, I was testing this out and I noticed an extra item is included in the resulting Array:

$ node -v
v8.6.0
$ npm install array.prototype.flatmap
+ [email protected]
$ node -e "console.log(require('array.prototype.flatmap')([1, 2, 3], a => [a]))"
[ 1, 2, 3, <1 empty item> ]

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on Greenkeeper branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet.
We recommend using:

• CircleCI
• Travis CI
• Buildkite
• CodeShip
• Azure Pipelines
• TeamCity
• Buddy
• AppVeyor
  But Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please click the 'fix repo' button on account.greenkeeper.io.

An in-range update of es-abstract is breaking the build 🚨

The dependency es-abstract was updated from 1.17.0-next.1 to 1.17.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

es-abstract is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

• ❌ Travis CI - Branch: The build canceled.

---

Commits

The new version differs by 12 commits.

• 91c2c22 v1.17.0
• 96719b9 [Dev Deps] update @ljharb/eslint-config
• c52fa59 [Fix] GetIntrinsic: IE 8 has a broken Object.getOwnPropertyDescriptor
• fb308ec [Deps] update is-callable, string.prototype.trimleft, string.prototype.trimright
• b84552d [Dev Deps] update tape
• 9be0385 [Refactor] GetIntrinsic: further simplification
• 0c7f99a [Tests] add .eslintignore
• e2df4de [Dev Deps] update object-is
• 158ed34 [Deps] update is-regex
• 3567ae9 [Refactor] GetIntrinsic: remove the internal property salts, since % already handles that
• 84c50fb [Dev Deps] update object.fromentries
• f0b1083 [meta] remove unused Makefile and associated utils

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴