Back to Explore

es-shims/iterator-helpers

GitHub
3 updates · last 90 days1 watchersOpen source

Last release: 1 month ago

Provides an ESnext-compliant iterator helpers shim or polyfill for sync iterators, intended to work in older environments down to ES3. It adds helper methods like map, filter, reduce, and others to iterator constructors or Iterator.prototype (and is useful for build tooling and testing).

Project status

  • The repo appears actively maintained, with multiple v1.3.x updates published in March to April 2026 (latest activity timestamp shown as 2026-04-13).
  • Update cadence is irregular but ongoing: v1.3.0 was followed by v1.3.1 about one day later (2026-03-11 to 2026-03-12), then v1.3.2 arrived about a month after v1.3.1 (2026-04-10).

AI summary generated Today

AI-generated from public sources. May be inaccurate. Report

Recent updates

  • v1.3.2

    1 month ago

    v1.3.2 makes extensive internal changes to iterator-helpers implementations, primarily around spec-compliant iterator closing and early-error handling. The GitHub release notes were not provided, but the code diff shows both behavioral changes (IteratorClose/IteratorStepValue handling) and a notable module export shape change across many entrypoint files.

  • v1.3.1

    2 months ago

    Release v1.3.1 contains a targeted change to the `Iterator.prototype.includes` polyfill implementation. The provided publisher release notes are empty, so the actual behavior change is only visible by inspecting the code diff.

  • v1.3.0

    2 months ago

    Release v1.3.0 was published on 2026-03-11, but no release notes were provided by the publisher. Without documented changes, developers should review the actual diff between the previous version and v1.3.0 to identify potential API, behavior, and configuration changes.

  • v1.2.2

    5 months ago

    No release notes were provided for v1.2.2. The code diff shows a broad internal refactor, largely upgrading the project to es-abstract 2025 algorithms and changing some iterator helper behaviors (notably string handling modes and generator state handling), without any corresponding release-note detail.

  • v1.2.1

    12/20/2024

    No publisher release notes were provided for v1.2.1. The repository documentation instead reflects this release primarily through a changelog entry and the actual code changes, which include iterator-spec compliance fixes and dependency refactors.

  • v1.2.0

    11/4/2024

    v1.2.0 introduces new iterator helpers, Iterator.zip and Iterator.zipKeyed, including support for mode (shortest, longest, strict) and longest-padding behavior. The change also introduces new internal infrastructure for joint-iteration semantics (closing multiple iterators, plural underlying iterator slots), and updates several existing helpers to match the new internal slot shape.

    Features
  • v1.1.0

    10/9/2024

    Version v1.1.0 adds a new iterator helper, `Iterator.concat`, including implementation, polyfill selection, and shim wiring into the package’s auto-shim entrypoints. The release notes were not provided by the publisher, so the changelog and code changes (new exports and new shimming behavior) are not documented there.

    Features
  • v1.0.19

    4/25/2024

    v1.0.19 primarily updates iterator helper polyfills for drop, filter, flatMap, and map to account for a V8/Chromium bug (Chromium issue 336839115). The repo also bumps the es-abstract dependency and removes some unused internal algorithms (AOs), with corresponding test and documentation adjustments.

  • v1.0.18

    3/15/2024

    Release v1.0.18 has no publisher release notes provided. The code diff shows a dependency refresh (notably moving from es-abstract 2023 algorithm modules to es-abstract 2024) plus a targeted change in generator completion handling.

  • v1.0.17

    2/13/2024

    Release v1.0.17 was published on 2024-02-13, but the publisher provided no release notes. Because no change log details are available, developers should treat this upgrade as potentially containing undocumented changes and verify compatibility by checking the code diff and running the test suite.