assertive-as-promised
Advanced tools
Comparing version 1.0.2 to 1.0.3
@@ -0,1 +1,7 @@ | ||
### 1.0.3 | ||
* docs: announce deprecation due to assertive>2.1.0 - **[@dbushong](https://github.com/dbushong)** [#3](https://github.com/groupon/assertive-as-promised/pull/3) | ||
- [`e81494e`](https://github.com/groupon/assertive-as-promised/commit/e81494e2bfb7970ffc6f0d832df28490ddf97749) **docs:** announce deprecation due to assertive>2.1.0 | ||
### 1.0.2 | ||
@@ -2,0 +8,0 @@ |
{ | ||
"name": "assertive-as-promised", | ||
"version": "1.0.2", | ||
"version": "1.0.3", | ||
"description": "Extends assertive with promise support", | ||
@@ -5,0 +5,0 @@ "license": "BSD-3-Clause", |
@@ -7,2 +7,30 @@ # Assertive for Promises | ||
# DEPRECATED | ||
As of `assertive-2.1.0`, this functionality has been rolled into | ||
[assertive] itself. The only functional change is that you can no longer | ||
pass functions-which-return-promises as arguments to `resolves()` and | ||
`rejects()` - you should replace things like: | ||
```coffee | ||
assert = require 'assertive-as-promised' | ||
assert.rejects -> doSomething('blah') | ||
``` | ||
with | ||
```coffee | ||
assert = require 'assertive' | ||
# this version will explode your test if there is a synchronous throw | ||
# during the invocation of doSomething() (which may be a good thing - | ||
# you can test for that behavior separately with assert.throws()) | ||
assert.rejects(doSomething('blah')).then (err) -> ... | ||
# this version will turn any synchronous throw into a rejection which will | ||
# be available as err | ||
Promise = require 'bluebird' | ||
assert.rejects(Promise.try -> doSomething('blah')).then (err) -> | ||
``` | ||
## How to Use | ||
@@ -9,0 +37,0 @@ |
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
New author
Supply chain riskA new npm collaborator published a version of the package for the first time. New collaborators are usually benign additions to a project, but do indicate a change to the security surface area of a package.
Found 1 instance in 1 package
11788
114
0