Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
3.15.0
->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
New Contributors
Full Changelog: avajs/ava@v4.3.0...v4.3.1
v4.3.0
Compare Source
What's Changed
throws
andthrowsAsync
assertions now take a function to test error messages, by @il3ven in https://github.com/avajs/ava/pull/2995t.log()
messages, by @il3ven in https://github.com/avajs/ava/pull/3013Full 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
sortTestFiles()
inava.config.js
files by @erezrokah in https://github.com/avajs/ava/pull/2968ava.config.json
files are encountered by @razor-x in https://github.com/avajs/ava/pull/2962deepEqual
assertion by @RebeccaStevens in https://github.com/avajs/ava/pull/2969Fixes
ava --version
works again by @novemberborn in https://github.com/avajs/ava/pull/2961New Contributors
Full Changelog: avajs/ava@v4.0.1...v4.1.0
v4.0.1
Compare Source
What's Changed
Full Changelog: avajs/ava@v4.0.0...v4.0.1
v4.0.0
: AVA 4Compare Source
We're celebrating the new year with the official AVA 4 release! 🎊
npm install -D ava
The cool new stuff 🆒
Worker threads 🧑💼
By default, test files are now run in worker threads! Huge thanks to @dnlup for landing this.
Test files should run a little quicker, since it's easier to spin up a worker thread than a child process. You can use
--no-worker-threads
on the command line, orworkerThreads: false
in your AVA configuration, to fall back to using child processes.Shared workers are no longer experimental 🎊
Shared workers are no longer experimental. This is a powerful feature that loads a program in a worker thread in AVA's main process and then communicate with code running in the test workers. This enables your tests to better utilize shared resources during a test run, as well as providing opportunities to set up these resources before tests start (or clean them up after).
When you use watch mode, shared workers remain loaded across runs.
Improved test selection 🤳
AVA selects test files based on your
package.json
orava.config.*
configuration files. When used on the CLI you can then provide patterns to select a subset of these files.You can now pass a folder and AVA will select the test files contained therein. Or you can provide a specific JavaScript file and AVA will run it even if it wasn’t selected by your configuration.
If AVA finds files based on the configuration, but none of those were selected to the CLI arguments, it now prints a warning.
Better monorepo support 🚝
AVA now looks for
ava.config.*
files in parent directories, until it finds a directory with a.git
directory (or file). This lets you specify AVA configuration at the top of your monorepo and still run AVA from within each package.New snapshot format 📸
@ninevra has worked tirelessly on landing a new snapshot format. It contains all information necessary to regenerate the report file. This allows for snapshots to be updated even if tests or assertions are skipped.
Previously failing test files run first 🏃
AVA now records which test files failed in the previous run. It then prioritizes testing these files when you run AVA again. Thanks @bunysae!
ESM support 🤾
AVA 4 comes with full ES module support. Both ESM and CJS entrypoints are provided so that you can use it no matter how you manage your project.
The
ava.config.js
file is now treated as CJS or ESM depending on module type configured in thepackage.json
file.ava.config.mjs
is now supported.If you use JavaScript files with non-standard extensions you can configure AVA to import them.
Note that dependency tracking in watch mode does not yet work with ES modules.
Dedicated macro factory with type inference 🏭
test.macro()
returns an object that can be used withtest()
and hooks. Thet.context
type is inherited fromtest
. When used with TypeScript this gives much better type inference.Like with AVA 3, regular functions that also have a
title
property that is a string-returning function are supported. However the type checking won’t be as good.Source maps 🗺
AVA now uses the source map support that’s built in to Node.js itself. This should give better stack traces. However we’re not sure yet what happens if you load a program that automatically modifies stack traces.
Line number selection (where
npx ava test.js:5
runs the test at line 5) now uses source maps and so should work better with TypeScript files.Assertions as type guards 💂
Most assertions now return a boolean indicating whether they passed. If you use AVA with TypeScript, you can use this as a type guard. Thanks @jmarkham828!
(This is not supported for
t.snapshot()
and the "throws" assertions.)Breaking changes 💥
AVA 4 requires at least Node.js 12.22, 14.17, 16.4 or 17. Node.js 10 is no longer supported.
If installed globally, AVA will no longer use any locally installed version. Install locally and run with
npx ava
instead. When running test files from another project that also has AVA installed, those test files will now fail to run (because they'll try and use that other AVA version).Ecosystem 🏞
@ava/babel
has been removed. We haven’t seen enough contributions to that package to recommend it for AVA 4. We’d be open to reinstating it in the future (just as we’d be open to support any other compilation provider).avajs/[email protected]
or newer.esm
package has been removed.Configuration 🗒
ava.config.js
now follows the module type configured inpackage.json
.ava.config.*
files may be found that are outside your project directory.Tests and assertions 🥼
test.meta.file
andtest.meta.snapshotDirectory
are now file URL strings.test()
andt.try()
no longer take an array of test implementations. Use a loop instead.t.throws()
andt.throwAsync()
assertions can no longer be called with anull
value for the expectations argument.test.cb()
andt.end()
have been removed. Use async functions andutil.promisify()
instead.t.teardown()
now executes in last-in-first-out order.Snapshots 📸
npx ava -u
to rebuild your snapshots after upgrading.t.snapshot()
no longer works in hooks.t.snapshot()
no longer takes an options argument allowing you to customize the snapshot ID.TypeScript 🪛
instanceOf
expectation oft.throws()
andt.throwsAsync()
assertions must now be anError
constructor.test.macro()
when declaring macros.unknown
.Meta
replacesMetaInterface
, other types withInterface
suffixes now use theFn
suffix. There may be some other changes too.4b4b2f6
t.throws()
andt.throwsAsync()
returnundefined
when the assertion fails. The type definition now matches this behavior.Other changes 🤓
--config
argument may now point to a file that is not alongside thepackage.json
file.t.timeout()
, AVA itself won’t time out until your test does. Thanks @OhYash!.test
and.spec
extensions from file names, as well astest-
prefixes.New Contributors
Full changelog since RC 1: avajs/ava@v4.0.0-rc.1...v4.0.0
Full changelog since AVA 3: avajs/ava@v3.15.0...v4.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.
This PR was generated by Mend Renovate. View the repository job log.