Skip to content

Update chai: 4.1.2 → 4.3.4 (minor)

Depfu Bot requested to merge depfu/update/yarn/chai-4.3.4 into master

Welcome to Depfu 👋

This is one of the first three pull requests with dependency updates we've sent your way. We tried to start with a few easy patch-level updates. Hopefully your tests will pass and you can merge this pull request without too much risk. This should give you an idea how Depfu works in general.

After you merge your first pull request, we'll send you a few more. We'll never open more than seven PRs at the same time so you're not getting overwhelmed with updates.

Let us know if you have any questions. Thanks so much for giving Depfu a try!

Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ chai (4.1.2 → 4.3.4) · Repo · Changelog
Release Notes

4.3.4

This fixes broken inspect behavior with bigints (#1321) (#1383) thanks @vapier

4.3.3

This reintroduces Assertion as an export in the mjs file. See #1378 & #1375

4.3.1

This releases fixed an engine incompatibility with 4.3.0

The 4.x.x series of releases will be compatible with Node 4.0. Please report any errors found in Node 4 as bugs, and they will be fixed.

The 5.x.x series, when released, will drop support for Node 4.0

This fix also ensures pathval is updated to 1.1.1 to fix CVE-2020-7751

4.3.0

This is a minor release.

Not many changes have got in since the last release but this one contains a very important change (#1257) which will allow jest users to get better diffs. From this release onwards, jest users will be able to see which operator was used in their diffs. The operator is a property of the AssertionError thrown when assertions fail. This flag indicates what kind of comparison was made.

This is also an important change for plugin maintainers. Plugin maintainers will now have access to the operator flag, which they can have access to through an utilmethod calledgetOperator`.

Thanks to all the amazing people that contributed to this release.

New Features

  • Allow contain.oneOf to take an array of possible values (@voliva)
  • Adding operator attribute to assertion error (#1257) (@rpgeeganage)
  • The closeTo error message will now inform the user when a delta is required (@eouw0o83hf)

Docs

  • Add contains flag to oneOf documentation (@voliva)

Tests

  • Make sure that useProxy config is checked in overwriteProperty (@vieiralucas)
  • Add tests for contain.oneOf (@voliva )

Chores

  • Update mocha to version 6.1.4
  • Add node v10 and v12 to ci (@vieiralucas)
  • Drop support for node v4, v6 and v9 (@vieiralucas)
  • Fix sauce config for headless chrome (@meeber)
  • Update dev dependencies (@meeber)
  • Removed phantomjs dependency (#1204)

4.2.0

This is a minor release. Thank you to all of our contributors and users!

New Features

Bug Fixes

Performance

Style

Tests

Docs

Chores

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

👉 No CI detected

You don't seem to have any Continuous Integration service set up!

Without a service that will test the Depfu branches and pull requests, we can't inform you if incoming updates actually work with your app. We think that this degrades the service we're trying to provide down to a point where it is more or less meaningless.

This is fine if you just want to give Depfu a quick try. If you want to really let Depfu help you keep your app up-to-date, we recommend setting up a CI system:

  • Circle CI, Semaphore and Travis-CI are all excellent options.
  • If you use something like Jenkins, make sure that you're using the Github integration correctly so that it reports status data back to Github.
  • If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with depfu/.

Depfu Status

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands
@​depfu rebase
Rebases against your default branch and redoes this update
@​depfu recreate
Recreates this PR, overwriting any edits that you've made to it
@​depfu merge
Merges this PR once your tests are passing and conflicts are resolved
@​depfu close
Closes this PR and deletes the branch
@​depfu reopen
Restores the branch and reopens this PR (if it's closed)
@​depfu pause
Ignores all future updates for this dependency and closes this PR
@​depfu pause [minor|major]
Ignores all future minor/major updates for this dependency and closes this PR
@​depfu resume
Future versions of this dependency will create PRs again (leaves this PR as is)

Merge request reports