Skip to content

Update dependency ava to v6 - autoclosed#445

Closed
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/ava-6.x
Closed

Update dependency ava to v6 - autoclosed#445
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/ava-6.x

Conversation

@renovate
Copy link

@renovate renovate bot commented Dec 5, 2023 •
edited
Loading

This PR contains the following updates:

Package Change Age Confidence
ava (source) 4.0.1 → 6.4.1 age confidence

Release Notes

avajs/ava (ava)

v6.4.1

Compare Source

What's Changed

New Contributors

Full Changelog: avajs/ava@v6.4.0...v6.4.1

v6.4.0

Compare Source

What's Changed

Interactive watch mode filters

@​mmulet did fantastic work to spearhead interactive watch mode filters. You can now filter test files by glob patterns, and tests by matching their titles. It's just like you already could from the CLI itself, but now without exiting AVA 🚀 #​3372

As part of this work we've removed the "sticky" .only() behavior #​3381

Examples

We've been remiss in merging #​3335 which updates the examples to use AVA 6. It's done now, examples are up to date and it's all due to @​tommy-mitchell 👏

New Contributors

Full Changelog: avajs/ava@v6.3.0...v6.4.0

v6.3.0

Compare Source

What's Changed

New Contributors

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

v6.2.0

Compare Source

What's Changed

  • Add filterNodeArgumentsForWorkerThreads option in #​3336
  • Add Node.js 23 to supported engines (and test matrix) in #​3346

New Contributors

Full Changelog: avajs/ava@v6.1.3...v6.2.0

v6.1.3

Compare Source

What's Changed

New Contributors

Full Changelog: avajs/ava@v6.1.2...v6.1.3

v6.1.2

Compare Source

What's Changed

Full Changelog: avajs/ava@v6.1.1...v6.1.2

v6.1.1

Compare Source

What's Changed

Full Changelog: avajs/ava@v6.1.0...v6.1.1

v6.1.0

Compare Source

What's Changed

  • Implement registerCompletionHandler() by @​novemberborn in #​3283

    AVA 6 expects test code to clean up gracefully when the tests are complete, allowing the test environment (worker thread or child process) to exit. If this does not happen, AVA will report a timeout. You can use registerCompletionHandler() to perform any other clean up (or indeed exit the process) after AVA has completed the test execution. See the description here.

  • Fix potential bug with watch mode when no failed test files are written by @​novemberborn in #​3287

  • Fix ava/internal ESM type module by @​codetheweb in #​3292

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

v6.0.1

Compare Source

What's Changed

Full Changelog: avajs/ava@v6.0.0...v6.0.1

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

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

v5.3.1

Compare Source

What's Changed

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

v5.3.0

Compare Source

What's Changed

New Contributors

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

v5.2.0

Compare Source

What's Changed

New Contributors

Full Changelog: avajs/ava@v5.1.1...v5.2.0

v5.1.1

Compare Source

What's Changed

Full Changelog: avajs/ava@v5.1.0...v5.1.1

v5.1.0

Compare Source

What's Changed

  • Output logs for tests that remain pending when AVA exits by @​kevo1ution in #​3125
  • Check for --config file extensions after they fail to load, allowing custom loaders by @​panva in #​3135

New Contributors

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

v5.0.1

Compare Source

Despite the major version bump this is a relatively minor release. Node.js 12 is no longer supported. The type definitions are now distributed to be compatible with TypeScript 4.7 or newer.

npm install --save-dev ava

Breaking Changes

  • AVA now requires Node.js 14.19, 16.15 or 18. #​3043
  • Type definition distribution assumes at least TypeScript 4.7. #​3041
  • We're now exporting types rather than interfaces. #​3096

Improvements

New Contributors

Full Changelog: avajs/ava@v4.3.3...v5.0.1

v5.0.0

Compare Source

Despite the major version bump this is a relatively minor release. Node.js 12 is no longer supported. The type definitions are now distributed to be compatible with TypeScript 4.7 or newer.

It's available as a pre-release under the next tag for the next few weeks:

npm install --save-dev ava@next

Breaking Changes

  • AVA now requires Node.js 14.19, 16.15 or 18. #​3043
  • Type definition distribution is no longer compatible with TypeScript versions before 4.7. #​3041
  • We're now exporting types rather than interfaces. #​3096

Improvements

New Contributors

Full Changelog: avajs/ava@v4.3.3...v5.0.0

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

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

New Contributors

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

v4.1.0

Compare Source

New features

Fixes

New Contributors

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: 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 was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added the dependencies Pull requests that update a dependency file label Dec 5, 2023
@renovate
Copy link
Author

renovate bot commented Dec 5, 2023 •
edited
Loading

⚠ 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 /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2024-05-05T23_22_45_860Z-debug-0.log

@renovate renovate bot force-pushed the renovate/ava-6.x branch from ed63c15 to ae152e9 Compare December 6, 2023 22:51
@renovate renovate bot force-pushed the renovate/ava-6.x branch from ae152e9 to a6f7171 Compare January 21, 2024 20:23
@renovate renovate bot force-pushed the renovate/ava-6.x branch from a6f7171 to 6a071cb Compare January 29, 2024 23:30
@renovate renovate bot force-pushed the renovate/ava-6.x branch from 6a071cb to 9a6214d Compare February 28, 2024 22:54
@renovate renovate bot force-pushed the renovate/ava-6.x branch from 9a6214d to 99edace Compare May 5, 2024 23:22
@renovate renovate bot force-pushed the renovate/ava-6.x branch from 99edace to 21e0150 Compare October 27, 2024 14:06
@renovate
Copy link
Author

renovate bot commented Oct 27, 2024 •
edited
Loading

⚠️ 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-02-17T20_39_46_097Z-debug-0.log

@renovate renovate bot force-pushed the renovate/ava-6.x branch from 21e0150 to ab7226f Compare May 2, 2025 16:03
@renovate renovate bot force-pushed the renovate/ava-6.x branch from ab7226f to 8c0f5bb Compare June 7, 2025 21:57
@renovate renovate bot force-pushed the renovate/ava-6.x branch from 8c0f5bb to 84be05d Compare July 12, 2025 21:31
@renovate renovate bot changed the title Update dependency ava to v6 Update dependency ava to v6 - autoclosed Feb 27, 2026
@renovate renovate bot closed this Feb 27, 2026
@renovate renovate bot deleted the renovate/ava-6.x branch February 27, 2026 21:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

@maccyber maccyber

@zrrrzzt zrrrzzt

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@maccyber @zrrrzzt