This is a spec-compliant shim/polyfill for `Array.prototype.includes`, implemented to work in older JavaScript environments down to ES3. It provides a drop-in `includes(array, value[, fromIndex])` function and can also expose a `shim()`/`getPolyfill()` result when `Array.prototype.includes` is missing.
Project status
- Maintenance status: The upstream GitHub repo shows a recent push on 2026-09-09, which suggests the project is still being worked on. However, the most recent published updates in the provided history are v3.1.9 (2025-06-02), so there is a gap between ongoing activity and documented published changes.
- Update cadence: Historically, published updates are infrequent (multi-year gaps are common). From 2025-06-02 to today (2026-09-10), there is no newer version listed in the provided summaries, indicating a slower release cadence despite recent upstream activity.
AI summary generated
Recent updates
v3.2.0
v3.2.0 introduces new TypeScript declaration files for array-includes and updates the includes/polyfill/shim behavior to be more spec-accurate. The runtime implementation change removes an Array.prototype.indexOf-based fast path and the shim now updates Array.prototype[Symbol.unscopables] for includes. Release notes from the publisher were not provided, so these changes may not be fully communicated to consumers.
Featuresv3.1.9
v3.1.9 primarily updates internal implementation details and dependency versions, including moving to newer `es-abstract` (2025) and switching utility imports to newer packages (`call-bound`, `math-intrinsics`). No publisher release notes were provided for this version, so changes are inferred from the actual diff.
v3.1.8
v3.1.8 primarily updates internal implementation dependencies and test tooling. The only functional code changes shown are module substitutions for core abstract operations (RequireObjectCoercible, ToObject, SameValueZero) and the corresponding dependency version bumps.
v3.1.7
Release v3.1.7 was published, but no release notes were provided by the publisher. No developer-facing changes, fixes, or migration guidance can be extracted from the available information.
v3.1.6
v3.1.6 primarily bumps internal dependency versions and updates implementation to use newer es-abstract (2022) modules. The release notes are missing (none provided), so the changes below are only visible via the code diff.
v3.1.5
v3.1.5 makes this package more robust by adjusting how it decides whether to use the native Array.prototype.includes or fall back to the provided polyfill implementation. The release notes provided by the publisher are empty, but the code diff shows dependency, tooling, CI, and test-script changes in addition to this runtime behavior adjustment.
v3.1.4
Release v3.1.4 updates core implementation details of the Array.prototype.includes shim, primarily by moving to newer es-abstract (2021) helpers and making the negative fromIndex math use an intrinsic Math.max instead of a direct Math.max call. The release notes provided by the publisher are empty (none supplied), so most behavior-impacting changes are effectively undocumented from that source.
v3.1.3
Release v3.1.3 primarily updates dependencies (runtime and dev), adjusts CI/workflow behavior, and tweaks published package contents by ignoring workflow files and coverage artifacts. The functional code diff is minimal, with no direct library implementation changes shown in the provided diff.
v3.1.2
No release notes were provided by the publisher for v3.1.2. The code change set is primarily internal refactoring: it migrates to newer `es-abstract` modules and `call-bind`/`get-intrinsic`, and adjusts how the polyfill implementation is invoked to remove direct reliance on `.apply`.
v3.1.1
v3.1.1 ships a compatibility fix for including values on IE < 9 by avoiding reliance on string index access. The publisher-provided release notes are missing, but the repo changelog and diff indicate dependency bumps, a Makefile removal, and added string test coverage.
v3.1.0
Release v3.1.0 was published on 2019-12-11, but no release notes were provided by the publisher. There is no documented information about new features, breaking changes, bug fixes, security updates, or migration steps in the provided release data.