Version 1.0.0

@stackline/is-empty

Check whether a value is "empty".

Independent maintenance of is-empty 1.2.0. Original authors and licenses are retained.

Installation

# Preserve existing imports with an npm alias
npm install is-empty@npm:@stackline/is-empty@1.0.0
# Or use the scoped package name in your imports
npm install @stackline/is-empty@1.0.0

Node.js: See compatibility notes. Read the compatibility and maintenance notes before migrating.

Usage and API

The reference below may retain upstream package names. Use the alias installation above to run those imports with this Stackline release.

@stackline/is-empty

Independent maintenance fork of is-empty@1.2.0. Original API, module format, runtime dependency ranges, and supported Node.js engines are preserved.

npm install @stackline/is-empty
# Preserve existing imports with an npm alias:
npm install is-empty@npm:@stackline/is-empty@1.0.0

See UPSTREAM.md for the exact source and issue review, and CHANGELOG.md for focused maintenance changes. Development and release tooling runs on Node.js 24; that does not change the library runtime requirement.

Maintained by Stackline. Issues · npm.

Upstream documentation

is-empty

Check whether a value is empty.

Installation

$ npm install is-empty
$ npm test

Example

var empty = require('is-empty');

empty([]);              // true
empty({});              // true
empty('');              // true
empty(0);               // true
empty(function(){});    // true
empty(null);            // true
empty(undefined);       // true
empty(new Map());       // true
empty(new Set());       // true
empty(new Error());     // true

empty(true);            // false
empty(false);           // false
empty(['a', 'b']);      // false
empty({ a: 'b' });      // false
empty('string');        // false
empty(42);              // false
empty(function(a,b){}); // false
empty(new Map([['key', 'value']])); // false
empty(new Set([1]));    // false
empty(new Error('fail'))// false

API

isEmpty(value)

Check whether value is empty.

License

MIT

Upstream issues and maintenance review

Upstream and issue review

Base: ianstormtaylor/is-empty, npm is-empty@1.2.0, commit 56ac2424f4f15866ae5274e15f5d2b41d38749b5. Full Git history and upstream attribution are retained. Last npm publication: 2017-02-01T16:39:49.434Z. Release inactivity does not by itself prove abandonment.

Review: 2026-09-29T00:21:53.835309+00:00. Source coverage: Most recently updated 100 open and 30 closed issue/PR entries; PRs removed. This is triage evidence, not a claim of exhaustive review.

Keep existing value semantics: invalid dates (#12), Intl/non-enumerable objects (#10), function arity (#9), whitespace (#14), and null-prototype objects are compatibility behavior, not changed by this fork. Closed #1, #2 and #8 are covered by the selected upstream tests (length properties, booleans and the string Error). Closed #5 is addressed by pinned development tools. No runtime defect was confirmed; lib/index.js is unchanged.

Reviewed issue entries

ianstormtaylor/is-empty#12 (open): Question: should invalid date be considered as empty?
ianstormtaylor/is-empty#10 (open): isEmpty(window.Intl) supposed to be false in Chrome
ianstormtaylor/is-empty#9 (closed): The empty of functions
ianstormtaylor/is-empty#14 (closed): Blank spaces are considered "not empty"
ianstormtaylor/is-empty#8 (closed): return true for string 'Error'
ianstormtaylor/is-empty#1 (closed): Returns true for an Object with a length property
ianstormtaylor/is-empty#2 (closed): Returns true for boolean true value
ianstormtaylor/is-empty#5 (closed): Be more specific with dependency versions

Release changes

Stackline changes

1.0.0 — 2026-09-28

Independent maintenance fork of is-empty 1.2.0. Preserve published API, module exports and runtime engine compatibility. Keep existing value semantics: invalid dates (#12), Intl/non-enumerable objects (#10), function arity (#9), whitespace (#14), and null-prototype objects are compatibility behavior, not changed by this fork. Closed #1, #2 and #8 are covered by the selected upstream tests (length properties, booleans and the string Error). Closed #5 is addressed by pinned development tools. No runtime defect was confirmed; lib/index.js is unchanged.

Pinned development tools, real API and packed-consumer checks, GitHub CI/CodeQL gates, exact-artifact npm provenance and immutable release evidence are added. See UPSTREAM.md for limits of issue triage.

Release files and references

Package bytes, npm provenance and the immutable GitHub release were verified for this version. Security checks describe the reviewed release; documented compatibility risks and upstream reports are not blanket claims of resolution.