1.1.0

New features

AVA now exports a meta object. Currently, you can retrieve the path of the test file being run:

import test from 'ava';

console.log('Test currently being run: ', test.meta.file);

import {meta} from 'ava';

console.log('Test currently being run: ', meta.file);

This is useful in helpers that need to know the test file. bccd297

Bug fixes and other improvements

• t.log() now works in hooks d187712

• Error output for improper usage of t.throws() once again links to the correct documentation dc552bc

• We've added a section on webpack aliases to the Babel recipe c3bcbf2

• We've updated the Vue recipe for Babel 7, and added a section on webpack aliases c3bcbf2

All changes 📚

v1.0.1...v1.1.0

Thanks 💌

💖 Huge thanks to @fitztrev, @forresst, @astrob0t, @pearofducks, @coreyfarrell and @dflupu for helping us with this release. We couldn’t have done it without you!

Get involved ✌️

We welcome new contributors. AVA is a friendly place to get started in open source. We have a great article on getting started contributing and a comprehensive contributing guide.

1.0

AVA 1.0 🚀

Back in January we started work on the 1.0 release, taking the opportunity to upgrade to Babel 7 and follow its beta releases. It's been a year where we made massive improvements to AVA. It's also been a year with many exciting events in our personal lives. Be it honeymoons & weddings, work & friends, naturalizations and international relocations.

So, we're done. Or, rather, we're just beginning. Testing can be a drag. AVA helps you get it done. Its concise API, detailed error output, embrace of new language features and process isolation let you write tests more effectively. So you can ship more awesome code or do non-programming things.

Starting now we'll push out patches and new features more regularly. And, when the time comes, ship a 2.0 and a 3.0 and so forth. If you like what we're doing, why not try and contribute? We're a friendly bunch and we could use your help to make AVA even better.

We couldn't have gotten here without the nearly one hundred people who've contributed more, and the many more who suggested improvements, reported bugs and provided feedback. And, of course, everyone who's used AVA. Thank you for your enthusiasm and support.

Mark & Sindre

What's new & improved

Assertions

New t.throws() behavior & t.throwsAsync()

We've rewritten t.throws() so it behaves better, has better error output and lets you write better tests:

• The assertion takes a first thrower argument. It must throw an exception, or your test fails. Throwing other values like strings also causes your test to fail.
• The exception must be an error object.
• The assertion returns the exception.

You have a few ways of asserting that the exception is as designed. You can pass a second argument:

• If you pass a function it should be a constructor: the exception must be an instance of it. Previously you could pass a validation function. This is no longer possible.
• If you pass a string: the exception's message should be equal to it.
• If you pass a regular expression: the exception's message should match it.

The most exciting new feature though is that you can pass an expectation object. A combination of the following expectations is supported:

t.throws(fn, {code: 'ENOTFOUND'}) // err.code === 'ENOTFOUND'
t.throws(fn, {code: 9}) // err.code === 9
t.throws(fn, {instanceOf: SyntaxError}) // err instanceof SyntaxError
t.throws(fn, {is: expectedErrorInstance}) // err === expectedErrorInstance
t.throws(fn, {message: 'expected error message'}) // err.message === 'expected error message'
t.throws(fn, {message: /expected error message/}) // /expected error message/.test(err.message)
t.throws(fn, {name: 'SyntaxError'}) // err.name === 'SyntaxError'

This makes tests like these much easier to write:

// Old assertion
const err = t.throws(fn, TypeError)
t.is(err.message, 'Expected a string')

// New assertion
t.throws(fn, {
	instanceOf: TypeError,
    message: 'Expected a string'
})

We've removed promise support from t.throws() and t.notThrows(). Use the new t.throwsAsync() and t.notThrowsAsync() assertions instead. Support for observables has been removed completey.

The original behavior was both hard to explain and hard to express in Flow and TypeScript. Now, if you have a function that throws a synchronous error, use t.throws() (or t.notThrows()). If you have a promise that should reject, or an asynchronous function that should fail, use await t.throwsAsync() (or await t.notThrowsAsync()).

Generally speaking, you should be able to replace every occurence of await t.throws with await t.throwsAsync, and await t.notThrows with await t.notThrowsAsync. A transform file for jscodeshift is available in this Gist. Run it like:

$ npx jscodeshift -t https://gist.githubusercontent.com/novemberborn/c2cdc94020083a1cafe3f41e8276f983/raw/eaa64c55dfcda8006fc760054055372bb3109d1c/transform.js test.js

Change test.js to a glob pattern that matches your test files. See the jscodeshift CLI usage documentation for further details.

Bound assertion methods

Assertion methods are now bound to the test, meaning you can provide them as direct arguments to other functions. A contrived example:

const assertEach = (arr, assert) => {
  arr.forEach(value => assert(value));
};

test('all are true', t => {
  assertEach(getArray(), t.true);
});

Whilst not strictly assertions, t.plan() and t.log() are now also bound to the test.

BigInt

As part of our Node.js 10 support you can now use BigInt values in t.deepEqual() and t.snapshot(). Note that this is still a stage-3 proposal.

Babel 7

AVA now uses Babel 7, with support for babel.config.js files. We'll automatically use your project's Babel configuration. Babel options must now be specified in a testOptions object. This will allow us to add source related options in the future.

Our @ava/stage-4 preset is now accessible via ava/stage-4. We've added transforms for the latest ES2018 features where available (and even an ES2019 one!). You can also disable ava/stage-4 entirely:

package.json:

{
  "ava": {
    "babel": {
      "testOptions": {
        "presets": [
          ["ava/stage-4", false]
        ]
    }
    }
  }
}

Or, you can disable just ES module compilation:

package.json:

{
  "ava": {
    "babel": {
      "testOptions": {
        "presets": [
          ["ava/stage-4", {"modules": false}]
        ]
      }
    }
  }
}

The powerAssert option and command line flags have been removed. You can now disable AVA's test enhancements by setting compileEnhancements to false. You can also disable AVA's Babel pipeline entirely:

package.json:

{
  "ava": {
    "babel": false,
    "compileEnhancements": false
  }
}

Serial hooks and context

Hooks declared using test.serial will now execute serially. Only one of those hooks will run at a time. Other hooks run concurrently. Hooks still run in their declaration order.

Note that concurrent tests run concurrently. This means that .beforeEach() and .afterEach() hooks for those tests may also run concurrently, even if you use test.serial to declare them.

t.context can now be used in .before and .after hooks.

CLI

Pass flags to your test

AVA now forwards arguments, provided after an -- argument terminator, to the worker processes. Arguments are available from process.argv[2] onwards.

npx ava test.js -- hello world

There's a new recipe on how to use this.

Previously AVA populated process.argv[2] and process.argv[3] with some undocumented internal values. These are no longer available.

Resetting AVA's cache

The --no-cache CLI flag has been replaced by a --reset-cache command. The latter resets AVA's regular cache location. You can still disable the cache through the cache configuration option.

npx ava --reset-cache

Configuration

Introducing ava.config.js

You can now configure AVA through an ava.config.js file. It must be placed next to the package.json, and you mustn't have any "ava" options in the package.json file. Export the configuration as a default:

export default {
    babel: {
        extensions: ['js', 'jsx']
    }
};

Or export a factory function:

export default ({projectDir}) => ({
    babel: {
        extensions: ['js', 'jsx']
    }    
});

Following our convention to use ES modules in test files, we're expecting ES modules to be used in the configuration file. If this is causing difficulties please let us know in #1820.

Configurable test & helper file extensions

You can now tell AVA to run test files with extensions other than js! For files that should be compiled using Babel you can specify babel.extensions:

package.json:

{
  "ava": {
    "babel": {
      "extensions": ["js", "jsx"]
    }
  }
}

Or define generic extensions, e.g. for use with TypeScript:

package.json:

{
  "ava": {
    "compileEnhancements": false,
    "extensions": ["ts"],
    "require": [
      "ts-node/register"
    ]
  }
}

Note that AVA still assumes test & helper files to be valid JavaScript. They're still precompiled to enable some AVA-specific enhancements. You can disable this behavior by specifying "compileEnhancements": false.

Snapshots

Adding new snapshots no longer causes the Markdown files to become malformed. Snapshots are now consistent across operating systems. If you've previously generated snapshots on Windows, you should update them using this release.

We now support BigInt and <React.Fragment> in t.snapshot(). We've also improved support for the Symbol.asyncIterator well-known symbol. Unfortunately these changes are not backwards compatible. You'll need to update your snapshots when upgrading to this release.

We've improved how AVA builds snapshot files to better support precompiled projects. Say, if you compile your TypeScript test files using tsc before running AVA on the build output. AVA will now use the source map to figure out the original filename and use that as the b...

1.0.0-rc.2

Release Candidate Two 🎷

Okay then, barring any surprises, the next release is the 1.0. But first, there's some changes we want to get out while we work on the celebratory blog post 😉

Please give this release a try and let us know of any problems. And as always with pre-releases, be sure to install an exact dependency. However unlikely, there may still be breaking changes between now and the final 1.0 release:

npm install --save-dev --save-exact ava@next

Please see the release notes for the previous betas:

• beta 1
• beta 2
• beta 3
• beta 4
• beta 5
• beta 6
• beta 7
• beta 8
• release candidate 1

Highlights

Better snapshot files for pre-built files

We've improved how AVA builds snapshot files to better support precompiled projects. Say, if you compile your TypeScript test files using tsc before running AVA on the build output. AVA will now use the source map to figure out the original filename and use that as the basis for the snapshot files. You'll have to manually remove snapshots generated by previous AVA versions. a130a9e

Set default title using parameters syntax

Macros can generate a test title. Previously, AVA would call the title function with an empty string if no title was given in the test declaration. Now, it'll pass undefined instead. This means you can use default parameters. Here's an example:

import test from 'ava'

const failsToParse = (t, input) => {
	t.throws(parse(input))
}

failsToParse.title = (providedTitle = 'unexpected input') => `throws when parsing ${providedTitle}`

test('malformed', failsToParse, fs.readFileSync('fixtures/malformed.txt'))
test(failsToParse, Buffer.from('}', 'utf8'))

This is a breaking change if you were concatenating the provided title, under the assumption that it was an empty string. aa35f15

TypeScript now type-checks additional arguments used by macros

When using TypeScript, you must now type the arguments used by the macro 6f54db8:

import test, {Macro} from 'ava'

const failsToParse: Macro<[Buffer]> = (t, input) => {
	t.throws(parse(input))
}

failsToParse.title = (providedTitle = 'unexpected input') => `throws when parsing ${providedTitle}`

test('malformed', failsToParse, fs.readFileSync('fixtures/malformed.txt'))
test(failsToParse, '}') // ⬅️ fails to compile

Bug fixes and other improvements

• Correctly insert a trailing newline when appending new snapshot entries. bf00d79
• Better error messages when used with esm 37390e6
• Support Node.js 11 afe028a
• New recipe on how test webapps using AVA and Puppeteer 6ab6d35

All changes 📚

v1.0.0-rc.1...v1.0.0-rc.2

Thanks 💌

💖 Huge thanks to @forresst, @sh7dm and @qlonik for helping us with this release. We couldn’t have done it without you!

Get involved ✌️

We welcome new contributors. AVA is a friendly place to get started in open source. We have a great article on getting started contributing and a comprehensive contributing guide.

1.0.0-rc.1

Release Candidate One 🥁

With this release AVA supports babel.config.js files. We've also improved our cache invalidation when you change your Babel configuration, so we're just about ready to ship the final 1.0 release 🎉

Please give this release a try and let us know of any problems. And as always with pre-releases, be sure to install an exact dependency. There may still be breaking changes between now and the 1.0 release:

$ npm install --save-dev --save-exact ava@next

Please see the release notes for the previous betas:

• beta 1
• beta 2
• beta 3
• beta 4
• beta 5
• beta 6
• beta 7
• beta 8

Highlights

• babel.config.js support. ff09749 We're still looking for some help with updating the documentation, see #1816.
• Improved Babel cache invalidation. ff55236
• AVA now prints pending tests when timeouts occur, when using --verbose. 6d12abf

Deep-equal and (breaking) snapshot changes

We now support BigInt and <React.Fragment> in t.deepEqual() and t.snapshot(). We've also improved support for the Symbol.asyncIterator well-known symbol. Unfortunately these changes are not backwards compatible. You'll need to update your snapshots when upgrading to this release. 71eede7

Bug fixes and other improvements

• profile.js now handles extensions configuration. 30a80b6
• When using t.throws() with asynchronous functions, AVA now suggests you use t.throwsAsync() instead. f125b4d
• AVA now detects when you attempt to wrap ava.config.js configuration in an ava property. f93b341

All changes 📚

v1.0.0-beta.8...v1.0.0-rc.1

Thanks 💌

💖 Huge thanks to @grant37, @xxczaki, @jamiebuilds, @robertbernardbrown, @lo1tuma, @goooseman, @wmik and @vancouverwill for helping us with this release. We couldn’t have done it without you!

Get involved ✌️

We welcome new contributors. AVA is a friendly place to get started in open source. We have a great article on getting started contributing and a comprehensive contributing guide.

1.0.0-beta.8

Beta Eight 🖐🤞☝️

We're getting ever closer! As you may recall our 1.0 release has been in beta due to its dependency on Babel 7. Well, Babel 7.0.0 has shipped! Lots of hurrahs and love to the Babel team for getting to this milestone. You should go read their announcement post 🎊

With this beta AVA now supports Babel 7. Before we can ship our 1.0 release there's just two issues left to tackle:

• We need to make sure AVA works with babel.config.js files and update our documentation: #1816
• We need to improve our cache invalidation when you change your Babel configuration: #1817

If you'd like to help get the 1.0 release over the line, please give us a shout in the respective issues.

Meanwhile, despite the release saying Beta, you really should be using this version. There won't be any fixes for the 0.x releases. Just be sure to install an exact dependency, as SemVer doesn't really apply to these betas:

$ npm install --save-dev --save-exact ava@next

Please see the release notes for the previous betas:

• beta 1
• beta 2
• beta 3
• beta 4
• beta 5
• beta 6
• beta 7

Highlights

Babel 7.0.0!

Also, the code expectation in t.throws() and t.throwsAsync() may now be a number. 7f974cc

Bug fixes

• TTY support for process.stderr is now emulated in the worker processes. 99098cc
• profile.js once again works with snapshots. 846920a
• Missing test.serial.failing.only() and test.serial.failing.skip() implementations have been added. 0ecd0be
• Snapshots are now consistent across operating systems. If you've previously generated snapshots on Windows, you should update them using this release. 28fe4e8
• AVA is better at detecting whether it's Babel syntax plugins have already been included by the user. d3bfb73
• The default reporter now includes files that did not declare any tests in its final output. 40be597

All changes 📚

v1.0.0-beta.7...v1.0.0-beta.8

Thanks 💌

💖 Huge thanks to @jagoda, @okyantoro, @sharkykh, @Phrynobatrachus and @billyjanitsch for helping us with this release. We couldn’t have done it without you!

Get involved ✌️

We welcome new contributors. AVA is a friendly place to get started in open source. We have a great article on getting started contributing and a comprehensive contributing guide.

1.0.0-beta.7

Beta Seven 🖐🤞

We're getting really close now! As you may recall our 1.0 release has been in beta due to its dependency on Babel 7. Well, Babel 7 now has a release candidate! 🎉

AVA now supports Babel 7.0.0-rc.1. Before we can ship our 1.0 release there's just two issues left to tackle:

• We need to make sure AVA works with babel.config.js files and update our documentation: #1816
• We need to improve our cache invalidation when you change your Babel configuration: #1817

If you'd like to help get the 1.0 release over the line, please give us a shout in the respective issues.

Meanwhile, despite the release saying Beta, you really should be using this version. There won't be any fixes for the 0.x releases. Just be sure to install an exact dependency, as SemVer doesn't really apply to these betas:

$ npm install --save-dev --save-exact ava@next

Please see the release notes for the previous betas:

• beta 1
• beta 2
• beta 3
• beta 4
• beta 5
• beta 6

Highlights

Automatic spreading of test file runs across parallel CI jobs

AVA now automatically detects whether your CI environment supports parallel builds. Each build will run a subset of all test files, while still making sure all tests get executed. See the ci-parallel-vars package for a list of supported CI environments. c4f607c

Breaking changes

Asynchronous use of the t.throws() and t.notThrows assertions

Before this release, the t.throws() and t.notThrows() assertions supported promises and observables. AVA did require you to await calls to these assertions if you used them asynchronously (as of v0.19.0). We realized this behavior was both hard to explain and hard to express in Flow and TypeScript.

Therefore we've decided to make t.throws() and t.notThrows() work solely with synchronous exceptions. The new t.throwsAsync() and t.notThrowsAsync() assertions work with asynchronous assertions. To further simplify the implementation (and type definitions) we've removed support for observables. d5dd981 7babf6b

Generally speaking, you should be able to replace every occurence of await t.throws with await t.throwsAsync, and await t.notThrows with await t.notThrowsAsync. A transform file for jscodeshift is available in this Gist. Run it like:

$ npx jscodeshift -t https://gist.githubusercontent.com/novemberborn/c2cdc94020083a1cafe3f41e8276f983/raw/eaa64c55dfcda8006fc760054055372bb3109d1c/transform.js test.js

Change test.js to a glob pattern that matches your test files. See the jscodeshift CLI usage documentation for further details.

test export

We're no longer exporting the test() method as a named export. Where before you could use import {test} from 'ava', you should now write import test from 'ava'. d7c6b3d

Generator functions

We've dropped support for using generator functions as test implementations. This was a remnant of the dark days before async/await support. 02d768f

Dropped support for Node.js 9

Node.js 9 is no longer supported by Node.js itself. Per our support statement we're also dropping support in AVA. We're listing this here as a breaking change, but note that, in the future, we reserve the right to drop support for odd-numbered Node.js versions without bumping AVA's major version number. 359e14b

Bug fixes

• Adding new snapshots no longer causes the Markdown files to become malformed. 223f992
• User's esm settings no longer affect how we load the ava.config.js file. 6b6aa06
• PromiseLike typing in Flow has been improved. e0f914a
• AVA now detects when it's required from a Node.js REPL. 3ac2a8f
• Better colors for use on light terminal themes. 76a8ce8
• The assert module in Node.js 10 no longer crashes. 55e4021
• Source maps, generated by AVA when compiling test & helper files, now contain correct paths to the source files. c9361cb
• Watch mode now detects changes to test & helper files with custom extensions. 17a18de

All changes 📚

v1.0.0-beta.6...v1.0.0-beta.7

Thanks 💌

💖 Huge thanks to @CanRau, @coreyfarrell, @ivanschwarz, @jagoda, @jamiebuilds, @padmaia, @ronen and @sh7dm for helping us with this release. We couldn’t have done it without you!

Get involved ✌️

We welcome new contributors. AVA is a friendly place to get started in open source. We have a great article on getting started contributing and a comprehensive contributing guide.

1.0.0-beta.6

Beta Six 🖐☝️

A quick release to fix some issues with Beta 5, and to upgrade to [email protected]. Please see the release notes for the previous betas:

• beta 1
• beta 2
• beta 3
• beta 4
• beta 5

Bug fixes

• Custom extension support now works without having to disable the Babel pipeline b3f7a70
• The mini reporter is no longer selected if your terminal does not support it 09f2d87

Enhancements

• Error messages now link to the documentation appropriate for the version of AVA you're using 9cdc29b
• AVA recognizes TypeScript build errors when using ts-node/register 5cce79a
• We've updated the TypeScript recipe with details on how to use it with our new custom extensions support 199cc70

All changes 📚

v1.0.0-beta.5...v1.0.0-beta.6

Thanks 💌

💖 Huge thanks to @tobil, @TheDancingCode and @btkostner for helping us with this release. We couldn’t have done it without you!

Get involved ✌️

We welcome new contributors. AVA is a friendly place to get started in open source. We have a great article on getting started contributing and a comprehensive contributing guide.

1.0.0-beta.5.1

See Beta 5. This release fixes del not being listed as a production dependency.

1.0.0-beta.5

Beta Five 🖐

It's time for another beta release for AVA 1.0. As you may recall we're now using Babel 7, so whilst Babel is in beta, so is AVA. You may want to read the previous release notes to get up to speed.

And despite the release saying Beta, you really should be using this version. There won't be any fixes for the 0.x releases. Just be sure to install an exact dependency, as SemVer doesn't really apply to these betas:

$ npm install --save-dev --save-exact ava@next

Babel updates ✨ a5de369

AVA now supports [email protected]. There've been significant changes to Babel's config resolution, both in beta 45 and in earlier releases. As you may be aware, AVA tries hard to detect when your Babel config changes, or when you update your plugins and presets. It's proven too difficult to maintain our existing code path for this. With this release we're using Babel's new APIs to construct AVA's Babel configuration, but unfortunately this has caused drastic regressions in our ability to invalidate AVA's precompilation cache.

For now, when you update your Babel config, plugins or presets, first reset AVA's cache. Luckily we've made this a lot easier:

$ npx ava --reset-cache

We have some ideas on how to detect most changes like we did before. Please join us in #1817 if you want to help.

Babel now supports babel.config.js files. We're looking for help to update our documentation, add integration tests and ensure we use that configuration file by default. Come join #1816 to help out.

AVA now applies the ava/stage-4 preset last. If you're customizing or disabling the ava/stage-4 preset, you must do so in the testOptions configuration. AVA now also supports Babel configurations that exclude specific files from compilation.

Configurable test & helper file extensions 🎈 3533aba

You can now tell AVA to run test files with extensions other than js! For files that should be compiled using Babel you can specify babel.extensions:

{
    "ava": {
        "babel": {
            "extensions": ["js", "jsx"]
        }
    }
}

Or define generic extensions, e.g. for use with TypeScript:

{
    "ava": {
        "compileEnhancements": false,
        "extensions": ["ts"],
        "require": [
            "ts-node/register"
        ]
    }
}

Note that AVA still assumes test & helper files to be valid JavaScript. They're still precompiled to enable some AVA-specific enhancements. You can disable this behavior by specifying "compileEnhancements": false.

Introducing ava.config.js 🍹 16f4742

You can now configure AVA through an ava.config.js file. It must be placed next to the package.json, and you mustn't have any "ava" options in the package.json file. Export the configuration as a default:

export default {
    babel: {
        extensions: ['js', 'jsx']
    }
};

Or export a factory function:

export default ({projectDir}) => ({
    babel: {
        extensions: ['js', 'jsx']
    }    
});

Following our convention to use ES modules in test files, we're expecting ES modules to be used in the configuration file. If this is causing difficulties please let us know in #1820.

Optional catch binding ⚾️ ad2d96d

The Optional catch binding proposal just reached stage 4 in the TC39 process. You can use it in AVA today 🎉

try {
    t.truthy(someFunc());
} catch { /* ignore */ }

t.throws() supports a code expectation 🍯 179f26a

Node.js' built-in errors come with a code property. You can now easily test for them:

t.throws(() => {
	fs.readFileSync('./example.txt');
}, {code: 'EACCES'});

Other breaking changes 💥

• Test implementations are now called with null as the this value. a681ecf
• All reporters write to stdout. The stdout and stderroutput from workers is written to process.stderr. AVA will insert linebreaks in process.stdout after writing a chunk to process.stderrthat does not end in a line break. 57d180a
• The --no-cache CLI flag has been replaced by a --reset-cache command. The latter resets AVA's regular cache location. You can still disable the cache through the cache configuration option. 8c9c474 ebb3948

Other changes 🚲

• AVA now uses its own Chalk instance, so AVA's color settings no longer impact the code you're testing. 2bd570e
• Error serialization has been made smarter, especially if non-Error errors are encountered. 0dc141d
• Uncaught exceptions and unhandled rejections are now shown with a code excerpt. 57d180a
• In watch mode, files being rerun are now excluded from the previous failure count. 57d180a
• You should see fewer repeated test timeout messages. d8349f5
• Better compatibility with recent Flow versions. a76d462

All changes 📚

v1.0.0-beta.4...v1.0.0-beta.5

Thanks 💌

💖 Huge thanks to @emilyschultz, @hallettj, @isnifer, @Jaden-Giordano, @good-idea and @jamiebuilds for helping us with this release. We couldn’t have done it without you!

Get involved ✌️

We welcome new contributors. AVA is a friendly place to get started in open source. We have a great article on getting started contributing and a comprehensive contributing guide.

1.0.0-beta.4

A Spring release 🌸

Spring has come to those in the Northern Hemisphere, and to celebrate here's a new AVA release! It's the fourth beta release for AVA 1.0. You may want to read the previous release notes to get up to speed.

This release uses [email protected]. We're waiting for Babel 7 to go out of beta before releasing the 1.0 version of AVA itself. This doesn't mean that these releases are any less stable than our previous 0.x versions though! If your project itself doesn't use Babel, or if your tests aren't coupled to your use of Babel 6 you really should upgrade.

Both Babel's and AVA's beta releases can contain breaking changes that are not reflected in the version number. We're now pinning against the Babel beta releases, to avoid accidental updates. We recommend you do the same when installing this AVA beta release.

You can install this release using the next distribution tag:

$ npm install --save-dev --save-exact ava@next

Goodbye Gitter, hello Spectrum 👋

We've moved the community to Spectrum. Come say hello!

Node.js 4 🌇

As you may be aware, Node.js 4 LTS will no longer be maintained come April 30th. Ordinarily this is when we'd drop support as well, but since we're in pre-release mode we decided to drop support a little early. See our Support Statement for our reasoning. e196257

npx ✨

Last July, npm started shipping npx, an npm package runner. It's a great way of running both installed packages and running one-off commands without adding anything to your package.json file.

Because of npx we're no longer recommending you install AVA globally. Instead use npx ava to run the AVA version installed in your project. d3bade8

We've also removed the ava --init command. Instead run npx create-ava to add AVA to your package.json. 3311d69 319d079

Spring cleaning the assertions 🌼

We've removed the t.ifError() assertion. It worked the same as t.falsy(), so if you were using it please switch to t.falsy() instead. e444654

Goodbye @std/esm, hello esm 📦

The @std/esm module loader has graduated to plain esm. We've updated our integration as well. Huge congrats to the esm team! 84a884e

Type definition improvements 🎭

We've made more improvements to the type definitions. You can once again pass an error to t.end() without encountering type errors. Assertion skipping has also been brought in line with AVA's actual implementation. We've also added as much inline documentation as we could. ecc219a 53fb487

Documentation updates 📃

• We've included some examples of how to exclude test files using the glob syntax a510088
• The JSPM, webpack, React and Vue.js recipes have been updated for Babel 7 29d2c5d 04d88b5 a36422c 6bba766
• Examples in the TypeScript recipe has been updated to work in strict mode e9d417f

All changes 📚

v1.0.0-beta.3...v1.0.0-beta.4

Thanks 💌

💖 Huge thanks to @BusbyActual, @billyjanitsch, @Briantmorr, @jdalton, @malimichael, @martypdx, @clemtrek, @samuelli, @kugtong33 and @forresst for helping us with this release. We couldn’t have done it without you!

Get involved ✌️

We welcome new contributors. AVA is a friendly place to get started in open source. We have a great article on getting started contributing and a comprehensive contributing guide.