Back to Explore

inspect-js/is-weakmap

GitHub
2 watchersOpen source

Last release:

Provides a small JavaScript utility that checks whether a given value is a JS WeakMap. It is designed to work across realms and iframes, handling cases despite ES6 @@toStringTag, useful for runtime type checks.

Project status

  • Maintenance status: Evidence suggests the project is not in frequent release mode, but there has been at least some upstream activity recently (last upstream push 2026-01-13). Based on published updates, the most recent tagged update is v2.0.2 (2024-03-08), so it is effectively quiet for most of the recent period.
  • Update cadence: Published updates show long gaps, roughly 2019-12 to 2024-03 for the latest major tagged release series, and even earlier between 2015 and 2019, indicating an overall low release frequency.

AI summary generated

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

Recent updates

  • v2.0.2

    Release v2.0.2 updates the is-weakmap package with new TypeScript declaration files and modernizes the development toolchain and CI workflows. The functional runtime logic in index.js appears unchanged, but packaging and build-related configuration (package.json scripts, publishing behavior, and metadata) was significantly altered.

    BreakingFeatures
  • v2.0.1

    v2.0.1 primarily contains internal refactoring to improve compatibility with build tools, plus CI and development dependency updates. No functional API changes are evident from the diff, and the runtime export remains a function that checks whether a value is a WeakMap.

  • v2.0.0

    Release v2.0.0 was published, but no release notes or changelog content was provided by the publisher. As a result, the upgrade impact (new features, bug fixes, breaking changes, security updates) cannot be determined from the supplied release information alone.

  • v1.0.1

    Release v1.0.1 appears to be a tooling and repository-quality update rather than a runtime change. The module behavior (the exported WeakMap check) is effectively unchanged, while the test and lint setup was modified.

  • v1.0.0

    Release v1.0.0 was published on 2015-02-18. No release notes were provided by the publisher, so specific changes, fixes, or migration guidance are not documented in the provided material.