chore: bump up ava version to v6

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
ava (source)	^5.3.1 -> ^6.0.0

---

Release Notes

avajs/ava (ava)

v6.0.0

Compare Source

Breaking Changes

• AVA now requires Node.js versions 18.18, 20.8 or 21. Versions 14 and 16 are no longer supported. #​3251 #​3216

• When tests finish, worker threads or child processes are no longer exited through proces.exit(). If your test file does not exit on its own, the test run will time out. #​3260

• Changes to watch mode #​3218:

  • Watch mode can no longer be started via the ava.config.* or package.json configuration.
  • The ignoredByWatcher configuration has moved to the watchMode object, under the ignoreChanges key.
  • Watch mode now uses the built-in fs.watch() in recursive mode. This is supported on Linux in Node.js 20 or newer, and MacOS and Windows in Node.js 18 as well. There are caveats to keep in mind.

• Failed assertions now throw, meaning that any subsequent code is not executed. This also impacts the type definitions. #​3246

• Only native errors are now considered errors by the t.throws() and t.throwsAsync() assertions. Object.create(Error.prototype) is not a native error. #​3229

• Changes to modules loaded through the require configuration #​3184:

  • If such modules export a default function, this function is now invoked.
  • Local files are loaded through @ava/typescript if necessary.

Improvements

Rewritten watcher

The watcher has been rewritten. It’s now built on fs.watch() in recursive mode.

@vercel/nft is used to perform static dependency analysis, supporting ESM and CJS imports for JavaScript & TypeScript source files. This is a huge improvement over the previous runtime tracking of CJS imports, which did not support ESM.

Integration with @ava/typescript has been improved. The watcher can now detect a change to a TypeScript source file, then wait for the corresponding build output to change before re-running tests.

The ignoredByWatcher configuration has moved to the watchMode object, under the ignoreChanges key.

See #​3218 and #​3257.

Failed assertions now throw

Assertions now throw a TestFailure error when they fail. This error is not exported or documented and should not be used or thrown manually. You cannot catch this error in order to recover from a failure, use t.try() instead.

All assertions except for t.throws() and t.throwsAsync() now return true when they pass. This is useful for some of the assertions in TypeScript where they can be used as a type guard.

Committing a failed t.try() result now also throws.

See #​3246.

t.throws() and t.throwsAsync() can now expect any error

By default, the thrown error (or rejection reason) must be a native error. You can change the assertion to expect any kind of error by setting any: true in the expectation object:

t.throws(() => { throw 'error' }, {any: true})

See #​3245 by @​adiSuper94.

The require configuration is now more powerful

It now loads ES modules.

Local files are loaded through @ava/typescript if necessary, so you can also write these in TypeScript.

If there is a default export function, it is invoked after loading. The function is awaited so it can do asynchronous setup before further modules are loaded. Arguments from the configuration can be passed to the function (as a [structured clone](https://developer.mozilla.org/en-US/docs/Web/API/structuredClone)).

See #​3184 by @​sculpt0r.

Other changes worth noting

• Internal events can now be observed (experimentally). See #​3247 by @​codetheweb. It’s experimental and undocumented.
• You can now use t.timeout.clear() to restore a previous t.timeout(). #​3221
• Code coverage is flushed to disk at opportune moments. #​3220

New Contributors

• @​sculpt0r made their first contribution in /~https://github.com/avajs/ava/pull/3184
• @​ZachHaber made their first contribution in /~https://github.com/avajs/ava/pull/3233
• @​adiSuper94 made their first contribution in /~https://github.com/avajs/ava/pull/3245
• @​bricker made their first contribution in /~https://github.com/avajs/ava/pull/3250

Full Changelog: avajs/ava@v5.3.1...v6.0.0

---

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.

---

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

---

This PR has been generated by Mend Renovate. View repository job log here.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (56ace48) 68.65% compared to head (e4c6db2) 68.66%.

Additional details and impacted files

@@            Coverage Diff             @@
##           canary    #5195      +/-   ##
==========================================
+ Coverage   68.65%   68.66%   +0.01%     
==========================================
  Files         520      520              
  Lines       21423    21423              
  Branches     2016     2016              
==========================================
+ Hits        14707    14711       +4     
+ Misses       6261     6257       -4     
  Partials      455      455              

Flag	Coverage Δ
e2e-plugin-test	33.86% <ø> (-0.16%)	⬇️
e2etest	57.19% <ø> (ø)
e2etest-macos-latest-x64	∅ <ø> (∅)
e2etest-ubuntu-latest-x64	41.58% <ø> (ø)
e2etest-windows-latest-x64	∅ <ø> (∅)
server-e2etest	52.34% <ø> (+0.08%)	⬆️
server-test	69.64% <ø> (ø)
unittest	50.65% <ø> (-0.07%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[graphite-app]

Merge activity

• Dec 5, 1:07 AM: @Brooooooklyn added this pull request to the Graphite merge queue.
• Dec 5, 1:40 AM: @Brooooooklyn merged this pull request with the Graphite merge queue.

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠ Warning: custom changes will be lost.