power-assert
power-assert copied to clipboard
Power Assert in JavaScript. Provides descriptive assertion messages through standard assert interface. No API is the best API.
When two strings of characters are very different, the output displayed by power assert is confusing. May be using a Levenstein distance (or other) to display the first string entirely...
Currently, only the first frame is shown: ``` # src/foo/bar/baz.js:37 assert(_.isArray(nodes) && nodes.length > 0 && _.every(nodes, node => node instanceof Node)) | | | | | | | |...
This is the test case demonstrating the issue above (contrived test to show duplicate output): ``` test('Test retrieval of TagList props object', () => { const props = getDefaultTagListProps(); assert(props);...
So, something like this is a pretty common pattern: ``` assert(typeof wrap === 'function') ``` --- ``` AssertionError: # giraphe.es6.js:61 assert(typeof wrap === 'function') | | "object" false --- [string]...
It seems like there is a great infrastructure around `power-assert`. More than this you provide a way for other assertion libraries to empowerment which is awesome! Nevertheless it seems like...
So, for relatively simple assertions, it's possible to keep the entire assertion within the single `assert( … )` statement; but I have a few places in my code where monstrosities...
version: 1.4.1 SystemJS settings: ``` map = { "power-assert": "n:power-assert", }; packages = { "power-assert": { main: "build/power-assert.js", defaultExtension: "js" }, } ``` My code ``` ts import * as...
So cute :ice_cream: :star2: :heartbeat: ``` js assert("☺⛺✅㊗🆘🌀🌟🌾🍨🍬🍰🎃🎄🎍🎨🏃💞💤😭😒" === "☺⛺✅㊗🆘🌀🌟🌾🍨🍬🍰🎄🎍🎨🏃💞💤😭😒"); ``` ``` URIError: URI malformed at encodeURI (native) ```
Thanks for making power-assert possible! I'm working on a project that uses power-assert together with karma, mocha, rollup and coffeescript. To make it all work together, I needed to make...
Bumps [json5](https://github.com/json5/json5) from 2.2.0 to 2.2.3. Release notes Sourced from json5's releases. v2.2.3 Fix: [email protected] is now the 'latest' release according to npm instead of v1.0.2. (#299) v2.2.2 Fix: Properties...