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 upstream repository shows a recent push on 2026-05-25, which suggests ongoing maintenance, but the newest published update in the provided history is v2.0.2 (2025-08-25), so the frequency of end-user updates since then is unclear from the evidence shown.
- Update cadence: A relatively fast follow-up occurred between v2.0.1 and v2.0.2 (both dated 2025-08-25), but there is a ~10 month gap in the listed published
updatesafter v2.0.2 up to today (2026-06-11).
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.