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: The module looks mostly stable functionally, with recent work focused on build and TypeScript declaration updates rather than runtime API changes, but there is a long gap between tagged updates (latest tag 2024-03-08) and today (2026-09-10), suggesting quiet, intermittent maintenance rather than active day-to-day release cadence. An upstream push occurred on 2026-01-13, but no corresponding tagged update is shown in the provided history.
- Update cadence: Updates are infrequent and sporadic (notably 2015, 2019, then 2024), with large multi-year gaps between tags.
AI summary generated
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.
BreakingFeaturesv2.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.