Releases: chaijs/chai-as-promised
Releases · chaijs/chai-as-promised
5.3.0
20 Mar 22:52
Compare
Sorry, something went wrong.
No results found
Adds support for promises from jQuery >= 3.0.0. (@mgol , #122 )
5.2.0
20 Dec 15:38
Compare
Sorry, something went wrong.
No results found
Allows messages to be passed through for .should.become(value, message). (@klamping , #132 )
5.1.0
20 Dec 15:37
Compare
Sorry, something went wrong.
No results found
Adds support for Chai 3.x.
5.0.0
16 Apr 03:55
Compare
Sorry, something went wrong.
No results found
No changes since 4.3.2, but hopefully this time I won't have to unpublish.
4.3.2 (unpublished)
25 Mar 11:09
Compare
Sorry, something went wrong.
No results found
Updates the Chai peer dependency to Chai 2.1.2, since 4.3.1 introduced that requirement.
This release was unpublished since some people view upgrading a peer dependency as a breaking change.
4.3.1 (unpublished)
24 Mar 13:30
Compare
Sorry, something went wrong.
No results found
Fixes problems with compatibility between Chai as Promised and other Chai plugins. (#94 ,
@Ryckes and @joshperry )
This release was unpublished since it broke compatibility with Chai below 2.1.2 but did not correctly update its peer dependency requirement.
4.3.0
05 Mar 23:18
Compare
Sorry, something went wrong.
No results found
Adds the chaiAsPromised.transformAsserterArgs hook. (@stalniy )
4.2.0
18 Feb 19:13
Compare
Sorry, something went wrong.
No results found
Adds compatibility with Chai 2.x.
4.1.1
01 Mar 01:16
Compare
Sorry, something went wrong.
No results found
Fixes assert.becomes and assert.doesNotBecome to pass through the third message parameter. That is,
assert . becomes ( Promise . resolve ( { foo : "bar" } ) , { foo : "bar" } , "should become foobar-ish" ) ;
will now work. (@martletandco )
4.1.0
27 Oct 04:51
Compare
Sorry, something went wrong.
No results found
This release adds a new feature allowing you to configure the output promise by overriding chaiAsPromised.transferPromiseness. You can see the documentation in the README .
Credit to @sebv for proposing this feature in #37 and writing the first draft in #38 .