Update dependency chai-as-promised to v8 #21
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^5.1.0
->^8.0.0
Release Notes
chaijs/chai-as-promised (chai-as-promised)
v8.0.1
Compare Source
What's Changed
Full Changelog: chaijs/chai-as-promised@v8.0.0...v8.0.1
v8.0.0
Compare Source
What's Changed
New Contributors
Full Changelog: chaijs/chai-as-promised@v7.1.2...v8.0.0
v7.1.2
Compare Source
What's Changed
New Contributors
Full Changelog: chaijs/chai-as-promised@v7.1.1...v7.1.2
v7.1.1
: 7.1.1Compare Source
Fixes ESLint accidentally being included as a dependency since v7.0.0.
v7.1.0
: 7.1.0Compare Source
Fixes Chai's proxy protection for property assertions (when using Chai v4 or higher). (@meeber, #205)
v7.0.0
: 7.0.0Compare Source
The breaking change in this release is that it has started using syntax that is only supported on Node.js v4 and above, as previous versions of Node no longer are supported by the Node.js project itself. As such browser consumers will also need to take care to transpile when testing on older browsers.
Additionally, Chai as Promised now supports Chai v4 (@meeber).
v6.0.0
: 6.0.0Compare Source
In #167, @lddubeau made many improvements to edge cases that have plagued users:
rejectedWith
to behave more like Chai'sthrows
asserter..fulfilled
,.rejected
, and.rejectedWith
to change the asserter target to the fulfillment value or rejection reason, so that further assertions with.and
act on them..fulfilled
, when successful, to return a promise that fulfills with the fulfillment value.rejected
and.rejectedWith
, when successful, to return a promise that fulfills with the rejection reasonAlso, Chai as Promised now only supplies a CommonJS-style module. To get AMD or
<script>
-compatibility, use a bundler tool like browserify.Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.