is-bigint is a JavaScript utility that checks whether a value is an ES BigInt, including cases like `1n` and `Object(1n)`. It is useful for adding type guards before you use BigInt-specific logic in your code.
Project status
- The project shows signs of continued attention, with an upstream push on 2026-04-29, but the most recent published npm update was v1.1.0 on 2024-12-02, so day-to-day maintenance appears sporadic.
- Update cadence looks uneven, with no updates documented after v1.1.0 in late 2024 through today (2026-06-09). Earlier updates were years apart (for example 2021 and then 2024), suggesting a slow-moving library.
AI summary generated
Recent updates
v1.1.0
Release v1.1.0 has no publisher-provided release notes. The code diff indicates the main user-facing change is that the package now ships TypeScript type declarations (index.d.ts), alongside a dependency bump (has-bigints) and packaging/publish metadata updates (npmignore generation, publishConfig ignore).
Featuresv1.0.4
v1.0.4 updates the project tooling and packaging. The main functional change revealed by the diff is that `has-bigints` is now a runtime dependency (moved from devDependencies), while lint configuration files were cleaned up and a dev dependency (`tape`) was bumped.
v1.0.3
Release v1.0.3 was published on 2021-08-06, but no release notes were provided by the publisher. As a result, there is no documented information about new features, fixes, breaking changes, or security updates in this release.
v1.0.2
This release (v1.0.2) contains no provided release notes from the publisher. The code diff shows primarily CI workflow changes, metadata/documentation updates, and development tooling adjustments (lint/deps, publishing scripts, and npm packaging ignores), with no visible runtime/library code changes.
v1.0.1
v1.0.1 contains no documented release notes from the publisher. The diff shows a version bump plus mostly development and CI tooling changes (GitHub Actions migration, test instrumentation, and dependency lint/dev tooling updates), with no clear runtime/API changes.
v1.0.0
This release is tagged v1.0.0, but no release notes were provided by the publisher, so the changes in this version are not documented here. Developers should review the corresponding commits, changelog history, and API surface diffs before upgrading to identify potential breaking or functional changes.