Back to Explore

inspect-js/is-weakset

GitHub
2 watchersOpen source

Last release:

Determines whether a given JavaScript value is a JS WeakSet. Useful for type checking WeakSet instances, including cases across realms or iframes, and it accounts for ES6 @@toStringTag.

Project status

  • The repo appears to be in ongoing maintenance rather than abandoned, with an upstream push on 2026-01-13 (recent activity), though the most recent provided published updates are older (v2.0.4 in 2024-12-17).
  • Update cadence looks infrequent and irregular: published updates were released in 2019, 2021, 2024 (v2.0.2 in 2021, v2.0.3 in 2024, v2.0.4 in 2024), with a long historical gap between earlier versions and the jump to v2.x.

AI summary generated

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

Recent updates

  • v2.0.4

    v2.0.4 has no publisher release notes in the provided data. The code diff shows a small runtime refactor around how intrinsic methods are “bound” (switching from `call-bind/callBound` to `call-bound`), plus several CI and development tooling changes.

  • v2.0.3

    This release (v2.0.3) adds TypeScript type support and updates several project metadata and tooling pieces. There are no functional runtime changes apparent in the WeakSet detection logic, but packaging and dependency versions were updated.

    Features
  • v2.0.2

    Release v2.0.2 was published on 2021-12-13, but no release notes were provided by the publisher. As a result, no specific code changes, fixes, or migration details can be reliably extracted from the provided data.

  • v2.0.1

    No publisher release notes were provided for v2.0.1 in the supplied release_notes content. The code diff and repository changelog changes indicate a small behavioral refactor in index.js (removing top-level returns) plus minor dev dependency updates and a new CI workflow.

  • v2.0.0

    Release v2.0.0 was published on 2019-11-12, but no release notes were provided in the available data. As a result, the changes, potential breaking behavior, and any migration or security details cannot be determined from the publisher text.

  • v1.0.1

    v1.0.1 is a small maintenance release with no documented change log. The code diff shows only minor repo hygiene updates (test script adjustment and test file rename), plus a README addition.

  • v1.0.0

    Release v1.0.0 was published on 2015-02-18, but no release notes were provided by the publisher. As a result, there is no documented information here about new features, breaking changes, bug fixes, security, performance, dependencies, or migration steps.