should-type versions and release history

Inspect a published release before upgrading or adding a dependency. Each version reference keeps its metadata and provider measurements pinned to that exact npm version.

Published versions15
Stable versions15
Prereleases0
Releases published in the last 90 days0
Deprecated releases0
Latest npm dist-tag1.4.0

All available releases

VersionPublishedRuntime dependenciesTypesStatus
1.4.02016-08-14T09:37:58.660Z0Not declaredlatest
1.3.02016-08-08T13:45:45.546Z0Not declared
1.2.02016-08-08T12:46:54.721Z0Not declared
1.1.02016-08-04T09:20:21.494Z0Not declared
1.0.22016-06-10T11:21:16.140Z0Not declared
1.0.12016-05-23T13:08:27.470Z0Not declared
1.0.02016-05-23T10:48:08.145Z0Not declared
0.2.02015-06-18T10:54:16.508Z0Not declared
0.1.12015-06-06T10:12:53.979Z0Not declared
0.1.02015-06-04T10:08:16.932Z0Not declared
0.0.52015-04-22T11:06:44.403Z0Not declared
0.0.42015-01-08T15:09:20.870Z0Not declared
0.0.32014-12-12T12:02:46.458Z0Not declared
0.0.22014-12-12T11:05:43.065Z0Not declared
0.0.12014-11-06T13:21:34.009Z0Not declared

Choosing a version

The latest tag is selected by the publisher and is not a guarantee of compatibility. Prerelease and deprecated status remain visible. Check your Node.js range and peer requirements on the exact version page, then review the maintainer’s release notes before upgrading.

Removed or unpublished versions may be absent. Historical download charts cover all package versions and do not show adoption of an individual release.

npm release-history source — retrieved 2026-10-29T11:15:24.148Z