Update dependency ava to v4.3.3

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
ava (source)	4.0.1 → 4.3.3

---

Release Notes

avajs/ava (ava)

v4.3.3

Compare Source

Add compatibility with Node.js 18.8, thanks @​Brooooooklyn #​3091.

Full Changelog: avajs/ava@v4.3.1...v4.3.3

v4.3.2

Compare Source

v4.3.1

Compare Source

What's Changed

• When translating line numbers, check whether the source map entry has original values in #​3061
• Report error when parsing for line number selection in #​3062

New Contributors

• @​ericcornelissen made their first contribution in #​3048
• @​AlencarGabriel made their first contribution in #​3051
• @​binyamin made their first contribution in #​3028

Full Changelog: avajs/ava@v4.3.0...v4.3.1

v4.3.0

Compare Source

What's Changed

• We're now shipping type definitions compatible with TypeScript 4.7, by @​RebeccaStevens in #​3024
• throws and throwsAsync assertions now take a function to test error messages, by @​il3ven in #​2995
• Test failure summaries no longer duplicate t.log() messages, by @​il3ven in #​3013
• The number of timed-out tests is printed at the end of a run, by @​il3ven in #​3021
• We've documented how to load multiple instances of the same "shared" worker, by @​codetheweb in #​3009
• Links to translated documentation have been updated, by @​forresst in #​3037
• Node.js 17 has been removed from the test matrix, and Node.js 18 added in #​3039

Full Changelog: avajs/ava@v4.2.0...v4.3.0

v4.2.0

Compare Source

What's Changed

• Update Babel recipe for AVA 4 by @​il3ven in #​3000
• Document how GitHub Actions can be configured for parallel builds by @​codetheweb in #​3007
• Allow parallel builds to be disabled by @​il3ven in #​3001
• Improve typing of teardown methods by @​novemberborn in #​3003

New Contributors

• @​mefengl made their first contribution in #​2999
• @​il3ven made their first contribution in #​3000
• @​codetheweb made their first contribution in #​3007

Full Changelog: avajs/ava@v4.1.0...v4.2.0

v4.1.0

Compare Source

New features

• Allow customized sorting of test files prior to execution using sortTestFiles() in ava.config.js files by @​erezrokah in #​2968
• Warn when unsupported ava.config.json files are encountered by @​razor-x in #​2962
• Loosen type constraints for deepEqual assertion by @​RebeccaStevens in #​2969

Fixes

• ava --version works again by @​novemberborn in #​2961

New Contributors

• @​sikrinick made their first contribution in #​2958
• @​scottdotjs made their first contribution in #​2954
• @​gibson042 made their first contribution in #​2975
• @​erezrokah made their first contribution in #​2968
• @​razor-x made their first contribution in #​2962
• @​RebeccaStevens made their first contribution in #​2969

Full Changelog: avajs/ava@v4.0.1...v4.1.0

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ 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]

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: next-routes@1.4.2
npm ERR! Found: react@17.0.2
npm ERR! node_modules/react
npm ERR!   react@"17.0.2" from the root project
npm ERR!   peer react@"^17.0.2 || ^18.0.0-0" from next@12.1.0
npm ERR!   node_modules/next
npm ERR!     next@"12.1.0" from the root project
npm ERR!     peer next@">=7.0.0" from next-offline@5.0.5
npm ERR!     node_modules/next-offline
npm ERR!       next-offline@"5.0.5" from the root project
npm ERR!     1 more (next-routes)
npm ERR!   5 more (react-dom, react-icons, react-map-gl, styled-jsx, use-subscription)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^15.4.2 || ^16" from next-routes@1.4.2
npm ERR! node_modules/next-routes
npm ERR!   next-routes@"1.4.2" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: react@16.14.0
npm ERR! node_modules/react
npm ERR!   peer react@"^15.4.2 || ^16" from next-routes@1.4.2
npm ERR!   node_modules/next-routes
npm ERR!     next-routes@"1.4.2" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! 
npm ERR! For a full report see:
npm ERR! /tmp/renovate-cache/others/npm/_logs/2022-11-20T20_28_42_939Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate-cache/others/npm/_logs/2022-11-20T20_28_42_939Z-debug-0.log

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: next-routes@1.4.2
npm ERR! Found: react@17.0.2
npm ERR! node_modules/react
npm ERR!   react@"17.0.2" from the root project
npm ERR!   peer react@"^17.0.2 || ^18.0.0-0" from next@12.1.0
npm ERR!   node_modules/next
npm ERR!     next@"12.1.0" from the root project
npm ERR!     peer next@">=7.0.0" from next-offline@5.0.5
npm ERR!     node_modules/next-offline
npm ERR!       next-offline@"5.0.5" from the root project
npm ERR!     1 more (next-routes)
npm ERR!   5 more (react-dom, react-icons, react-map-gl, styled-jsx, use-subscription)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^15.4.2 || ^16" from next-routes@1.4.2
npm ERR! node_modules/next-routes
npm ERR!   next-routes@"1.4.2" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: react@16.14.0
npm ERR! node_modules/react
npm ERR!   peer react@"^15.4.2 || ^16" from next-routes@1.4.2
npm ERR!   node_modules/next-routes
npm ERR!     next-routes@"1.4.2" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /runner/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /runner/cache/others/npm/_logs/2026-03-08T10_09_50_959Z-debug-0.log