apollo-errors icon indicating copy to clipboard operation
apollo-errors copied to clipboard
verified publisher icon thebigredgeek

Update dependency chai to v6

Open renovate[bot] opened this issue 4 months ago • 0 comments

Note: This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
chai (source) 3.5.0 -> 6.2.1 age confidence

Release Notes

chaijs/chai (chai)

v6.2.1

Compare Source

What's Changed

New Contributors

Full Changelog: https://github.com/chaijs/chai/compare/v6.2.0...v6.2.1

v6.2.0

Compare Source

What's Changed

Full Changelog: https://github.com/chaijs/chai/compare/v6.1.0...v6.2.0

v6.1.0

Compare Source

What's Changed

  • build(deps-dev): bump tar-fs from 3.0.9 to 3.1.1 by @​dependabot[bot] in #​1706
  • feat: add eventEmitter (#​1693) Adds an event emitter for hooking into method/property creation in #​1693

Full Changelog: https://github.com/chaijs/chai/compare/v6.0.2...v6.1.0

v6.0.1

Compare Source

What's Changed

Full Changelog: https://github.com/chaijs/chai/compare/v6.0.0...v6.0.1

v6.0.0

Compare Source

BREAKING CHANGES

Chai is now bundled into a single file. The lib/*.js files are no longer present, and so any code that imports those files directly will need to change. The only file that can be imported now is ./index.js.

What's Changed

Full Changelog: https://github.com/chaijs/chai/compare/v5.3.2...v6.0.0

v5.3.3

Compare Source

What's Changed

Full Changelog: https://github.com/chaijs/chai/compare/v5.3.2...v5.3.3

v5.3.2

Compare Source

Reverts the removal of the bundled version of chai in 5.3.1

What's Changed

Full Changelog: https://github.com/chaijs/chai/compare/v5.3.1...v5.3.2

v5.3.1

Compare Source

What's Changed

Full Changelog: https://github.com/chaijs/chai/compare/v5.3.0...v5.3.1

v5.3.0

Compare Source

What's Changed

Full Changelog: https://github.com/chaijs/chai/compare/v5.2.2...v5.3.0

v5.2.2

Compare Source

What's Changed

Full Changelog: https://github.com/chaijs/chai/compare/v5.2.1...v5.2.2

v5.2.1

Compare Source

What's Changed

Mostly internal changes but @​SuperchupuDev realised the package.json engines field was out of date, so it has been updated to reflect that v5.0.0 onwards only supports Node >=18.

New Contributors

Full Changelog: https://github.com/chaijs/chai/compare/v5.2.0...v5.2.1

v5.2.0

Compare Source

What's Changed

New Contributors

Full Changelog: https://github.com/chaijs/chai/compare/v5.1.2...v5.2.0

v5.1.2

Compare Source

What's Changed

Full Changelog: https://github.com/chaijs/chai/compare/v5.1.1...v5.1.2

v5.1.1

Compare Source

What's Changed

New Contributors

Full Changelog: https://github.com/chaijs/chai/compare/v5.1.0...v5.1.1

v5.1.0

Compare Source

What's Changed

New Contributors

Full Changelog: https://github.com/chaijs/chai/compare/v5.0.3...v5.1.0

v5.0.3

Compare Source

Fix bad v5.0.2 publish.

Full Changelog: https://github.com/chaijs/chai/compare/v5.0.2...v5.0.3

v5.0.2

Compare Source

What's Changed

Full Changelog: https://github.com/chaijs/chai/compare/v5.0.1...v5.0.2

v5.0.0

Compare Source

BREAKING CHANGES

  • Chai now only supports EcmaScript Modules (ESM). This means your tests will need to either have import {...} from 'chai' or import('chai'). require('chai') will cause failures in nodejs. If you're using ESM and seeing failures, it may be due to a bundler or transpiler which is incorrectly converting import statements into require calls.
  • Dropped support for Internet Explorer.
  • Dropped support for NodeJS < 18.
  • Minimum supported browsers are now Firefox 100, Safari 14.1, Chrome 100, Edge 100. Support for browsers prior to these versions is "best effort" (bug reports on older browsers will be assessed individually and may be marked as wontfix).

What's Changed

New Contributors

Full Changelog: https://github.com/chaijs/chai/compare/4.3.1...v5.0.0

v4.5.0

Compare Source

What's Changed

Full Changelog: https://github.com/chaijs/chai/compare/v4.4.1...v4.5.0

v4.4.1

Compare Source

What's Changed

Full Changelog: https://github.com/chaijs/chai/compare/v4.4.0...v4.4.1

v4.4.0

Compare Source

What's Changed

  • Allow deepEqual fonction to be configured globally (4.x.x branch) by @​forty in #​1553

Full Changelog: https://github.com/chaijs/chai/compare/v4.3.10...v4.4.0

v4.3.10

Compare Source

This release simply bumps all dependencies to their latest non-breaking versions.

What's Changed

Full Changelog: https://github.com/chaijs/chai/compare/v4.3.9...v4.3.10

v4.3.9

Compare Source

Upgrade dependencies.

This release upgrades dependencies to address CVE-2023-43646 where a large function name can cause "catastrophic backtracking" (aka ReDOS attack) which can cause the test suite to hang.

Full Changelog: https://github.com/chaijs/chai/compare/v4.3.8...v4.3.9

v4.3.8

Compare Source

What's Changed

New Contributors

Full Changelog: https://github.com/chaijs/chai/compare/v4.3.7...v4.3.8

v4.3.7

Compare Source

What's Changed

Full Changelog: https://github.com/chaijs/chai/compare/v4.3.6...v4.3.7

v4.3.6

Compare Source

Update loupe to 2.3.1

v4.3.5

Compare Source

v4.3.4

Compare Source

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

v4.3.3: / 2021-03-03

Compare Source

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

v4.3.2: / 2021-03-03

Compare Source

This fixes a regression in IE11. See #​1380 & #​1379

v4.3.1: / 2021-03-02

Compare Source

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

v4.3.0: / 2021-02-04

Compare Source

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

Chores

v4.2.0: / 2018-09-25

Compare Source

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

New Features

Bug Fixes

Performance

Style

Tests

Docs

Chores

v4.1.2: / 2017-08-31

Compare Source

This release fixes a bug when running in certain environments, and includes a few minor documentation fixes.

Bug Fixes

Docs

v4.1.1: / 2017-08-05

Compare Source

This release includes a few bug and documentation fixes.

Bug Fixes

Docs

v4.1.0: / 2017-07-11

Compare Source

This release includes one new feature and a few bug fixes.

New Features

Bug Fixes

Chores

v4.0.2: / 2017-06-05

Compare Source

We have another bugfix release, addressing some issues for WebPack 1 users.

Bug Fixes

  • Revert getting version information from package.json, some bundler tools like Webpack do not come default with json loaders despite Node being able to handle this. This change moves back to hardcoding the version number in the codebase. (#​985, #​986)

v4.0.1: / 2017-05-31

Compare Source

4.0.1

Of course, any major release cannot go without a quick bugfix release shortly after - and here's ours!

Bug Fixes

  • Remove package.json browser field which was mistakenly added, and caused bundler tools like Browserify or Webpack to fail as it attempted to rebundle an already bundled file. (#​978, #​982)

v4.0.0: / 2017-05-26

Compare Source

4.0.0

4.0 has been a huge undertaking by the chai community! A lot has changed to ensure Chai 4 is a stable, reliable, well documented codebase. Here are just some of the major improvements:

  • almost all documentation has been rewritten, with detailed instructions on how assertions work, which flags they can be combined with and the best practices for how to use them.

  • deep equality has been rewritten from the ground up to support ES6 types like Map and Set, and better support existing types. It is now also much, much faster than before and allows us to bring some great improvements in upcoming releases.

  • we have made sure the deep flag now only ever does deep equality. Beforehand, it would sometimes also be used to test nested properties (for example expect(foo).to.have.deep.property('bar.baz'). For nested assertions, please now use the .nested flag.

  • many assertions have become more strict, which means you get better error messages explaining where things have gone wrong. For the most part, this wont mean error messages where there weren't error messages before, but it will mean better error messages to replace the, sometimes cryptic, default TypeError messages.

  • we've added detections and helpful error messages for common mistakes and typos. The error messages will, in some cases, point you to documentation or in other cases suggest alternatives. These messages will continue to be improved in future releases, so let us know if you have any suggestions!

Breaking Changes

  • We no longer support Node v0.10 and v0.12 (since their LTS has ended) (PRs: #​816, #​901)

  • Instead of allowing the user to write the path of a property, now the deep flag performs a deep equality comparison when used with the .property assertion. If you want the old behavior of using the dot or bracket notation to denote the property you want to assert against you can use the new .nested flag. (Related Issues: #​745, #​743, PRs: #​758, #​757)

    const obj = {a: 1};

// The `.deep` flag now does deep equality comparisons
expect({foo: obj}).to.have.deep.property('foo', {a: 1});

// Use the `nested` flag if you want to assert against a nested property using the bracket or dot notation
expect({foo: obj}).to.have.nested.property('foo.a', 1);

// You can also use both flags combined
const obj2 = {a: {b: 2}};
expect({foo: obj2}).to.have.deep.nested.property('foo.a', {b: 2});

    Please notice that the old methods which used the old behavior of the deep flag on the assert interface have been renamed. They all have had the deep word changed by the nested word. If you want to know more about this please take a look at #​757.

  • Previously, expect(obj).not.property(name, val) would throw an Error if obj didn't have a property named name. This change causes the assertion to pass instead. The assert.propertyNotVal and assert.deepPropertyNotVal assertions were renamed to assert.notPropertyVal and assert.notDeepPropertyVal, respectively. (Related Issues: #​16, #​743, #​758)

  • You can now use the deep flag for the .include assertion in order to perform a deep equality check to see if something is included on the target. Previously, .include was using strict equality (===) for non-negated property inclusion, but deep equality for negated property inclusion and array inclusion. This change causes the .include assertion to always use strict equality unless the deep flag is set. Please take a look at this comment if you want to know more about it. (Related Issues: #​743, PRs: #​760, #​761)

    const obj = {a: 1};
expect([obj]).to.deep.include({a:1});
expect({foo: obj}).to.deep.include({foo: {a:1}});

  • Fix unstable behavior of the NaN assertion. Now we use the suggested ES6 implementation. The new implementation is now more correct, strict and simple. While the old one threw false positives, the new implementation only checks if something is NaN (or not if the .not flag is used) and nothing else. (Related Issues: #​498, #​682, #​681, PRs: #​508)

    // Only `NaN` will be considered to be `NaN` and nothing else
expect(NaN).to.be.NaN;

// Anything that is not `NaN` cannot be considered as `NaN`
expect('randomString').not.to.be.NaN;
expect(true).not.to.be.NaN;
expect({}).not.to.be.NaN;
expect(4).not.to.be.NaN;

  • The Typed Array types are now truncated if they're too long (in this case, if they exceed the truncateThreshold value on the config). (Related Issues: #​441, PRs: #​576)

    var arr = [];
for (var i = 1; i <= 1000; i++) {
  arr.push(i);
}

// The assertion below will truncate the diff shown and the enormous typed array will be shown as:
// [ 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, ...  ] instead of printing the whole typed array
chai.expect(new Float32Array(100)).to.equal(1);

  • The assertions: within, above, least, below, most, increase, decrease will throw an error if the assertion's target or arguments are not numbers. (Related Issues: #​691, PRs: #​692, #​796)

    // These will throw errors, for example:
expect(null).to.be.within(0, 1);
expect(null).to.be.above(10);
expect(null).to.be.at.least(20);
expect(null).to.be.below(20);
expect(null).to.be.at.most(20);
expect(null).to.increase.by(20);
expect(null).to.decrease.by(20);

// This will not:
expect('string').to.have.a.lengthOf.at.least(3);

  • Previously, expect(obj).not.ownProperty(name, val) would throw an Error if obj didn't have an own property (non-inherited) named name. This change causes the assertion to pass instead. (Related Issues: #​795, #, PRs: #​744, #​810)*

    expect({ foo: 'baz' }).to.not.have.own.property('quux', 'baz');

  • The .empty assertion will now throw when it is passed non-string primitives and functions (PRs: #​763, #​812)

    // These will throw TypeErrors:
expect(Symbol()).to.be.empty;
expect(function() {}).to.be.empty;
expect(true).to.be.empty;
expect(1).to.be.empty

  • Assertion subject (obj) changes when using ownProperty or own.property and thus enables chaining. (Related Issues: #​281, PRs: #​641)

    expect({val: 20}).to.have.own.property('val').above(10);

  • The .change, .increase, and .decrease assertions changed from chainable method assertions to method assertions. They don't have any chaining behavior, and there's no generic semantic benefit to chaining them. (Related Issues: #​917, PRs: #​925)

// This will not work anymore because there is no benefit to chaining these assertions:
expect(function() {}).to.change.by(2)
expect(function() {}).to.increase.by(2)
expect(function() {}).to.decrease.by(2)

  • The utils (second argument passed to the chai.use callback function) no longer exports the getPathValue function. If you want to use that please use the pathval module, which is what chai uses internally now. (Related Issues: #​457, #​737, PRs: #​830)

  • (For plugin authors) Throw when calling _superon overwriteMethodif the method being overwritten is undefined. Currently if the method you are trying to overwrite is not defined and your new method calls _super it will throw an Error.(Related Issues: #​467, PRs: #​528) Before this change, calling _super would simply return this.

    // Considering the method `imaginaryMethod` does not exist, this would throw an error for example:
chai.use(function (chai, utilities) {
  chai.Assertion.overwriteMethod('imaginaryMethod', function (_super) {
    return function () {
      _super.apply(this, arguments);
    }
  });
});

// This will throw an error since you are calling `_super` which should be a method (in this case, the overwritten assertion) that does not exist
expect('anything').to.imaginaryMethod();

  • (*For plugin author

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 is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • [ ] If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

renovate[bot] avatar Aug 22 '25 15:08 renovate[bot]