assertive
assertive copied to clipboard
Assertive is a terse yet expressive assertion library
Bumps [json5](https://github.com/json5/json5) from 1.0.1 to 1.0.2. Release notes Sourced from json5's releases. v1.0.2 Fix: Properties with the name __proto__ are added to objects and arrays. (#199) This also fixes a...
Bumps [json5](https://github.com/json5/json5) and [tsconfig-paths](https://github.com/dividab/tsconfig-paths). These dependencies needed to be updated together. Updates `json5` from 1.0.1 to 2.2.3 Release notes Sourced from json5's releases. v2.2.3 Fix: [email protected] is now the 'latest'...
Bumps [minimist](https://github.com/substack/minimist) from 1.2.5 to 1.2.6. Commits 7efb22a 1.2.6 ef88b93 security notice for additional prototype pollution issue c2b9819 isConstructorOrProto adapted from PR bc8ecee test from prototype pollution PR See full...
Bumps [path-parse](https://github.com/jbgutierrez/path-parse) from 1.0.6 to 1.0.7. Commits See full diff in compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter...
This module cannot be installed by yarn after 3.0.0. > error [email protected]: The engine "yarn" is incompatible with this module. Expected version "0.0.0". Got "1.17.3" > error Found incompatible module....
The [nicer diffs](https://github.com/groupon/assertive/pull/30) look great - but when you compare to a function, it breaks: ```js assert.equal(function () {}, function () {}); // throws something about trying to call .split...
Add test for basic functionality when you `require('assertive')` in a browserified environment
This is kind of blurring the lines between `assertive` and `assertive-as-promised`, but given async functions this is the only thing I keep "poly-filling". For everything else the normal `assertive` works...
``` js assert.expect(2 > 3); ``` I want assertive to include the source line in the error, e.g. by capturing the stack trace in a smarter way.
_Brought up in https://github.com/groupon/assertive/pull/11_ - `assert.every`: check should pass for all elements - `assert.some`: check should pass for at least one element - `assert.notAll`: check should fail for at least...