which-boxed-primitive detects whether a given JavaScript value is a boxed primitive and returns the corresponding built-in constructor name (like Boolean, Number, or String), or null for unboxed primitives. It is designed to work across realms and iframes without relying on instanceof or mutable properties, which makes it useful for type checks in mixed execution contexts.
Project status
- The source looks at least somewhat actively maintained, with an upstream push as recent as 2026-03-19, but the newest published updates shown are v1.1.1 from 2024-12-16.
- Apparent update cadence is intermittent: a long gap from v1.0.2 (2020-12-14) to v1.1.0 (2024-12-02), then two quick updates in December 2024 (v1.1.0 on 2024-12-02, v1.1.1 on 2024-12-16).
AI summary generated Today
Recent updates
v1.1.1
12/16/2024The release v1.1.1 contains no published release notes. The only changes visible in the diff are version bumping and updates to a set of runtime and dev dependency versions.
v1.1.0
12/2/2024Release v1.1.0 primarily adds TypeScript type declarations and updates repository tooling (tests, CI workflows, linting, and publish scripts). The runtime implementation in index.js appears unchanged, aside from a JSDoc type import comment.
Featuresv1.0.2
12/14/2020Release v1.0.2 was published on 2020-12-14, but no release notes were provided by the publisher. As a result, there is no documented information about new features, fixes, breaking changes, or dependency updates for this version.
v1.0.1
8/11/2019Release v1.0.1 primarily updates the package metadata and npm publishing behavior. No functional runtime code changes are shown in the provided diff, only a change to the publish script and an added dev dependency.
v1.0.0
8/10/2019Release v1.0.0 was published on 2019-08-10, but no release notes were provided by the publisher. As a result, this release cannot be analyzed for documented new features, breaking changes, bug fixes, security updates, or migration steps from the release notes alone.