Provides `AssertionError` and `AssertionResult` classes for test and validation frameworks that implement a standardized AssertionError specification. Useful for returning or throwing consistent assertion outcomes from functions, including checking `.name`, `.ok`, or using `instanceof Error`.
Project status
- Maintenance status: The project is not clearly under steady active maintenance, as the most recent published update was v2.0.2 on 2025-08-25, and the update history shows long gaps between versions (not a frequent release cycle). There was an upstream push on 2026-05-25, but no additional tagged updates are shown in the provided history.
- Apparent update cadence: After a major rewrite (v2.0.0 in 2021-10-05), updates appear to have resumed briefly in Aug 2025 (v2.0.1, v2.0.2), then no further updates are listed up to 2026-09-10, suggesting a low cadence (more maintenance than ongoing iteration).
AI summary generated
Recent updates
v2.0.2
v2.0.2 removes the npm script named `posttest` from package.json. All other shown changes are limited to script configuration, and the `test` command itself remains the same.
Breakingv2.0.1
v2.0.1 is primarily a tooling and implementation refactor, moving the project to a Deno-based build/test flow. Release notes mention CI updates and the Deno refactor, but the diff also shows changes to packaging, type declaration strategy, and AssertionError stack trace behavior.
BreakingFeaturesv2.0.0
v2.0.0 is a rewrite of the package using TypeScript and ES6 classes. It introduces a new `AssertionResult` class and adds an `.ok` boolean property on both `AssertionError` and `AssertionResult`. The release notes are minimal and do not document several important module, typing, and behavioral changes visible in the code diff.
Features1.1.0
Release 1.1.0 primarily adds TypeScript type definitions for the AssertionError export. It also introduces a TypeScript compile-time test step and updates the package metadata to expose types.
Features1.0.2
This release is a small maintenance update that fixes incorrect stack traces when using PhantomJS. The change is intended to improve debugging output, without introducing new features or expected API changes.