type-check is a JavaScript library for validating the runtime types of values using a Haskell-like type syntax. It is useful for checking external input, testing, and adding extra safety to internal code, with helper functions to check types directly or reuse parsed type definitions.
Project status
- Maintenance status: The last upstream push was on 2023-07-18, and the most recent listed version update is 0.4.0 from 2020-04-03, so the source appears quiet/dormant rather than actively maintained as of 2026-06-09.
- Update cadence: Updates are sparse and far apart (notably 0.4.0 in 2020, with earlier releases in 2015 and then 2014-2013), indicating no regular cadence in the recent past.
AI summary generated
Recent updates
0.4.0
Release 0.4.0 has no publisher-provided release notes. The code diff shows an internal refactor of the type checker to thread options through nested checks, plus functional changes to how custom types and union parsing behave.
BreakingFeatures0.3.2
Release 0.3.2 contains no publisher-provided release notes. The code diff shows the package version bumped to 0.3.2, regenerated build artifacts using LiveScript 1.4.0, and multiple dependency and build-system changes (notably prelude-ls and browser bundle output).
0.3.1
Release 0.3.1 was published on 2014-04-08, but the publisher did not provide any release notes. As a result, there is no documented information here about new functionality, fixes, breaking changes, or dependency updates.
0.3.0
Release 0.3.0 updates type-check to support inline type comments using the `Identifier::` prefix form (eg `count::Number`). It changes the type tokenizer and parsing logic to recognize `::` and strips the comment token before parsing the actual type(s).
Features0.2.0
This release bumps the library version from 0.1.0 to 0.2.0. The only substantive code change is in how the `Maybe` type is parsed, which changes the resulting internal type-check evaluation order.
0.1.0
Release 0.1.0 was published on 2013-09-27, but no release notes were provided by the publisher. As a result, there is no documented information about new features, breaking changes, bug fixes, security updates, performance improvements, or migration steps.