ava
8.4.0 · 7 Nov 2026MIT575.3k / weekRepositoryHomepagenpmAtom feed
112 stable releases, newest first, by release line. Notes are quoted as the maintainers published them.
- 3.x
3.6.0
5 Apr 2020afterEach()andafterEach.always()hooks can now determine whether the test passed. Thank you @bunysae for contributing this! 8f312c0:afterEach()andafterEach.always()hooks can now determine whether the test passed. Thank you @bunysae for contributing this! 8f312c0:test('passes', t => t.pass()); test.afterEach(t => { if (t.passed) { // Do something because the test passed } else { // Do something because the test failed } });@mbiesiad has diligently translated our documentation to Polish. Thank you @kekuu for reviewing.
Also thank you @timgates42 for fixing a typo in our documentation. ede4f32
See v3.5.0...v3.6.0 for all changes.
3.5.0
1 Mar 2020When using
ava debug, you can now specify the address or hostname the inspector is available through by using the--hostoption. Thanks to @DYefimov for contributing this! 13d6651When using
ava debug, you can now specify the address or hostname the inspector is available through by using the--hostoption. Thanks to @DYefimov for contributing this! 13d6651See v3.4.0...v3.5.0 for all changes. Spoiler alert: it's just this one 😉
3.4.0
23 Feb 2020ava.config.jsfiles once again work with our@ava/typescriptpackage f4d4eddOur TypeScript definition no longer references
@types/node7a1dacf
Introducing the
t.try()assertionThe new
t.try()allows you to try assertions without causing the test to fail:test('do the thing', async t => { const attempt = () => t.try(async tt => { const result = await getResult() // getResult() can be flaky and sometimes throws :( tt.is(result, 'expected') }) const firstAttempt = await attempt() if (firstAttempt.passed) return firstAttempt.commit() t.log('Retrying (just once)') firstAttempt.discard() const secondAttempt = await attempt() secondAttempt.commit() })You can use any test implementation with
t.try(), including (arrays of) macros. You can decide what to do with attempts. You can even run attempts concurrently, so long as they don't use snapshot assertions.This is great building block for handling all kinds of advanced test scenarios. We can't wait to see what you'll do with it! Find out more in the assertion documentation.
This feature was previously behind an experimental flag. That flag has now been removed. If you have enabled the flag you'll have to update your AVA config. Also note that as of this release, attempt titles are always prefixed with the title of the parent test 7ee3a0e.
Once again, thank you @qlonik for contributing this new assertion.
In case you missed it: ESM support
As of the 3.3.0 release, AVA can load ESM test files! Check our updated ES Modules recipe for details.
Our ESM support is still incomplete. Progress is tracked in the ESM support project. Join us, won't you?
Other changes
The
t.throws()andt.throwsAsync()assertions can now be called withundefinedas the second argument. Previously, if you wanted to set an assertion message but did not want to provide any expectations for the thrown error you had to passnull. That's still allowed, of course. d0e2161 @stavalfiava.config.jsfiles once again work with our@ava/typescriptpackage f4d4eddOur TypeScript definition no longer references
@types/node7a1dacfWe've improved the error message shown when
test.cb()is used with asynchronous functions or observables f5a8c2b @toddkcarlsonThe Vue recipe has been updated to use
jsdom-globalinstead ofbrowser-env3f9c616 @Scrum
See v3.3.0...v3.4.0 for all changes.
3.3.0
9 Feb 2020AVA can now load ESM test files! 🎉Thank you @arlac77 for making this happen. Check our updated ES Modules recipe for details.
AVA can now load ESM test files! 🎉Thank you @arlac77 for making this happen. Check our updated ES Modules recipe for details.
Our ESM support is still incomplete. Progress is tracked in the ESM support project. Join us, won't you?
Other changes
See v3.2.0...v3.3.0 for all changes.
3.2.0
2 Feb 2020This release improves the integration with the new
@ava/typescriptpackage, which allows AVA to load pre-compiled TypeScript files.This release improves the integration with the new
@ava/typescriptpackage, which allows AVA to load pre-compiled TypeScript files.First, install the new
@ava/typescriptpackage:npm install --save-dev @ava/typescript@^1.1
Now let's assume your TypeScript files are in a
srcdirectory, output to abuilddirectory. Configure AVA like so:ava.config.jsfile:export default { typescript: { rewritePaths: { 'src/': 'build/' } } }Compile your TypeScript files and run your tests! Or, to run a specific test file, run
npx ava src/test.ts.For more examples see the
@ava/typescriptpackage.As exciting as this is, it's still early days. We need your help improving our TypeScript support. Check out the open issues.
Other changes
See v3.1.0...v3.2.0 for all changes.
3.1.0
26 Jan 2020AVA can now load pre-compiled TypeScript files!
AVA can now load pre-compiled TypeScript files!
First, install the new
@ava/typescriptpackage:npm install --save-dev @ava/typescript
Now let's assume your TypeScript files are in a
srcdirectory, output to abuilddirectory. Configure AVA like so:ava.config.jsfile:export default { typescript: { rewritePaths: { 'src/': 'build/' } } }Compile your TypeScript files and run your tests! Or, to run a specific test file, run
npx ava src/test.ts.For more examples see the
@ava/typescriptpackage.As exciting as this is, it's still early days. We need your help improving our TypeScript support. Check out the open issues.
Other changes
See v3.0.0...v3.1.0 for all changes.
3.0.0
19 Jan 2020- Breaking
**/__tests__/**/__helper__/**/* - Breaking
**/__tests__/**/__helpers__/**/* - Breaking
**/__tests__/**/__fixture__/**/*
We're proud to introduce AVA 3!
When we began AVA, JavaScript was very different. Most syntax you find familiar today was not supported by Node.js. Instead we relied on Babel to support that syntax before it made its way to Node.js itself.
These days most new stage-4 syntax is adopted quickly. It's often not necessary to transpile anything. Therefore we're removing our built-in Babel support from AVA itself.
Without Babel you'll have to resort to using
require()functions in your JavaScript files. But, you say, Node.js 13 supports ECMAScript Modules!Well, we're getting there. For a start, AVA now also looks for
.cjsfiles. And.mjsfiles are recognized too, but can't be loaded just yet. This also impactsava.config.jsfiles. If you'd like to help out delivering full.mjssupport check out the issues in the ESM support project.Removing Babel allowed us to simplify how test files are selected. Likely non-test files, inside "fixture" or "helper" directories are ignored. The same for files that are inside an underscore-prefixed directory. We've made some other breaking changes in this area so please do read the full release notes.
You can again pass glob patterns on the CLI. However these now filter the test files that AVA already selected based on the configuration. In other words you can't run files that wouldn't be run by invoking
npx ava.AVA now interrupts your tests if there's no progress for 10 seconds. Use the
timeoutconfiguration or--timeoutCLI option to change this.New features
Built-in debug mode
You can now debug individual test files using the V8 Inspector:
npx ava debug test.js
Connect to the debugger with Chrome DevTools. Or set up a debugger in VSCode.
Configurable Node.js arguments
You can now configure the arguments passed to Node.js itself when AVA starts its worker processes. Use the
nodeArgumentsconfiguration or combine with the--node-argumentsCLI option.All breaking changes
Supported Node.js versions
We now support Node.js 10, 12 and 13. The minimal versions are 10.18.0, 12.14.0 and 13.5.0 respectively.
Removing Babel
Utilize Babel with AVA by installing our
@ava/babelpackage and then enabling Babel by settingbabel: truein the AVA configuration. Having this as a separate package means it can evolve independently.The
compileEnhancementssetting has been moved into thebabelconfiguration. Consequently, thet.assert()assertion will only print its detailed information when you use Babel. And we won't be able to catch typical mistakes witht.throws()as well as we could before.The
ava/stage-4preset is now available from@ava/babel/stage-4. Our old@ava/babel-preset-transform-test-filesand@ava/babel-preset-stage-4packages are no longer maintained and not installed with AVA itself.ECMAScript Module Support
AVA now also looks for
.cjsand.mjstest files. That said,.mjsfiles cannot be loaded just yet.Also, when you add
"type": "module", AVA would really like to treat.jsfiles as ECMAScript Modules, but can't just yet.Similarly,
ava.config.cjsconfiguration files are now supported.ava.config.mjsfiles not just yet.With AVA 2, we loaded
ava.config.jsfiles using theesmpackage. To avoid confusion between the different module formats we now only supportexport defaultstatements. Noimport, no__filename. Configuration files that have dependencies should be written as a.cjsfile for now.Configuration files can only have
.cjs,.jsand.mjsextensions.The remaining work is tracked in the ESM support project.
File selection
When you use the default configuration AVA will no longer select files matching the following glob patterns:
- Breaking
**/__tests__/**/__helper__/**/* - Breaking
**/__tests__/**/__helpers__/**/* - Breaking
**/__tests__/**/__fixture__/**/* - Breaking
**/__tests__/**/__fixtures__/**/* - Breaking
**/test/**/helper/**/* - Breaking
**/test/**/helpers/**/* - Breaking
**/test/**/fixture/**/* - Breaking
**/test/**/fixtures/**/* - Breaking
**/tests/**/helper/**/* - Breaking
**/tests/**/helpers/**/* - Breaking
**/tests/**/fixture/**/* - Breaking
**/tests/**/fixtures/**/*
Additionally, when a file has a parent directory that starts with a single underscore, it can never be a test file.
test.jsfiles are only selected if they're next to thepackage.jsonfile, or inside top-levelsrcandsourcedirectories.We've removed the configuration of helpers. Previously, files selected by the
helpersglob patterns were never considered test files. Now that this configuration is no longer supported you'll need to ensure thefilespatterns exclude your helper files. If you're using Babel, you can configure the compilation of additional files .The
sourcesconfiguration has also been removed. Instead, use theignoredByWatcherconfiguration. Changes to files matched by these glob patterns will not cause the watcher to rerun tests.Negated
sourcespatterns must be used without the negation inignoredByWatcher:export default { - sources: ['!examples/**/*'] + ignoredByWatcher: ['examples/**/*'] }CLI changes
Internally we've replaced
meowbyyargs. We're not expecting things to break because of this, but you never know.Resetting the cache
The
--reset-cacheargument has been replaced by a properreset-cachecommand:npx ava reset-cache
File selection (again!)
AVA again accepts glob patterns via the CLI:
npx ava '**/api/**/*'
The way this work is that AVA first finds all test files, according to the configuration, and then filters to select just the files that also match the glob patterns passed via the CLI.
You can still pass paths to specific files:
npx ava src/api/test/my-api-test.js
However unlike with AVA 2, you can no longer specify test files that aren't already selected by AVA's configuration.
t.throws()andt.throwsAsync()assertionsThe second argument passed to these assertions must now be an
expectationobject. You can no longer pass the expected constructor, error message or regular expression.Other breaking changes
- Breaking
Support for old
esmversions has been removed. - Breaking
We've set a default test timeout of 10 seconds. This means that if no test results are received for 10 seconds, AVA forces its worker processes to quit.
- Breaking
The
NODE_PATHenvironment variable is no longer rewritten to ensure values are absolute paths. - Breaking
AVA longer fakes the TTY in worker processes.
Other changes
We've simplified how we identify observables. Any object returned by a test implementation that has a
subscribefunction is assumed to be an observable. AVA's type definition has been updated accordingly.The TAP reporter now reports hook failures as test failures.
We've added an example of module path mapping to our TypeScript recipe.
We've added a Selenium WebDriver JS recipe.
All changes
- 2.x
2.4.0
16 Sep 2019We've added the common pitfall of sharing variables across asynchronous tests 49b202f
We've updated the endpoint testing recipe to focus on the concept, not specific libraries 67e4dea
Experimental
t.try()assertionsWe're excited to get this out there, but it's not quite done yet. For now you have to opt in to this new feature. Being opt-in, we may make changes (breaking ones even!) until we feel this is stable.
To opt in, configure AVA with the following:
package.json:{ "ava": { "nonSemVerExperiments": { "tryAssertion": true } } }ava.config.js:export default { nonSemVerExperiments: { tryAssertion: true } };We'd love to hear your feedback. Please join us in this issue: #2250
Also, if you're looking to help out with the remaining issues so that we can ship this without the opt-in, have a look at this project: github.com/orgs/avajs/projects/1
Thanks again @qlonik!
Other changes
We've added the common pitfall of sharing variables across asynchronous tests 49b202f
We've updated the endpoint testing recipe to focus on the concept, not specific libraries 67e4dea
All changes
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.
2.3.0
18 Aug 2019AVA now prints an error when it receives non-existent test files on the command line. f01d05f
When using the TAP reporter, remaining tests are now included in failed test count. Failed hooks are no longer treated as test failures, and logs are printed. 8628976
Changes
We've fixed some bugs to improve watch mode. ffa62ce 9e8d28f
AVA now prints an error when it receives non-existent test files on the command line. f01d05f
When using the TAP reporter, remaining tests are now included in failed test count. Failed hooks are no longer treated as test failures, and logs are printed. 8628976
Internal errors that may occur for some edge cases are now printed. b27cb8d
TTY in the worker processes should follow the new APIs in Node.js 12.7.0 (when used with those Node.js versions). 7dcb473
AVA now handles stage-4 syntax like dynamic import, and stage-3 syntax like BigInt, numeric separators and class properties that are supported by V8. 9baca8c
AVA now supports dynamic import through our stage-4 preset.
AVA now uses
import-local@^3.0.2which fixes issues with Lerna projects.For our TypeScript users, we've changed the default type of
t.contexttounknown, in line with TypeScript's changes in their 3.5 release. 2fc7d56
All changes
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.
2.2.0
8 Jul 2019You can now specify an alternative config file, using the
--configCLI argument. This is useful if you want to run unit tests separately from integration tests, since you can have a config file specific to your integration tests which specifies different glob patterns. 2dae2bfEnhancements
You can now specify an alternative config file, using the
--configCLI argument. This is useful if you want to run unit tests separately from integration tests, since you can have a config file specific to your integration tests which specifies different glob patterns. 2dae2bfBug fixes
We're now faking the new
hasColors()method for better compatibility with Node.js 12. d399797Node.js 11
We've removed Node.js 11 from our test matrix. You should upgrade to Node.js 12. 90acbb9
All changes
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.
2.1.0
10 Jun 2019AVA's TypeScript definition now explicitly references the Node.js definition bb44da7
Did you know you can provide human-readable timeout values? We've now documented this. 486acaf
We're now including all stack trace lines in the TAP output (though we still pre-process them). ac212ba
Bug fixes
AVA's TypeScript definition now explicitly references the Node.js definition bb44da7
Enhancements
Did you know you can provide human-readable timeout values? We've now documented this. 486acaf
We're now including all stack trace lines in the TAP output (though we still pre-process them). ac212ba
Logs from successful hooks are now included in the TAP output. 007c7af
Our ESLint plugin helper has been updated to allow extensions and glob patterns to be overridden b3c9ea7
All changes
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.
2.0.0
1 Jun 2019The TypeScript definition once again allows
test.skip(macro)ba5cd80
Breaking changes
AVA now requires at least Node.js 8.9.4
Per the Node.js release schedule, the 6.x releases reach end of live on April 30th. Consequently we've removed support in AVA. We are now testing with Node.js 12 though. 3a4afc6
Test file and helper selection
We've been working on simplifying how test files and helpers are selected. First off, the
filesoption now only accepts glob patterns. If you configured it with directories before, please add/**/*to get the previous behavior.The
filesandsourcesoptions must now be arrays containing at least one pattern. It's no longer possible to override a default exclusion pattern, but we're looking at making these configurable separately.AVA used to treat all files inside a
helpersdirectory as test helpers. Finding these files could be really slow, however, and it also meant you couldn't have tests inside ahelpersdirectory. Instead you can now specify glob paterns to find these helpers:{ "ava": { "helpers": [ "**/helpers/**/*" ] } }Test files starting with an underscore are still recognized as helpers.
Files inside
fixturesdirectories are no longer ignored, and will now be treated as test files. The watcher now also watchesava.config.jsfiles.AVA now also selects files ending with
.spec.jswhen looking for tests, as well as looking intestsdirectories. 08e99e5 b1e54b1The CLI now only takes file paths, not glob patterns.
We'd like some help updating our ESLint plugin as well.
Snapshots in CI
When you run tests locally and add a new snapshot, AVA automatically updates the
.snapfile. However if you forget to commit this file and then run your CI tests, they won't fail because AVA quietly updates the.snapfile, just like it does locally.With this release, AVA will fail the
t.snapshot()assertion if it is run in CI and no snapshot could be found. 0804107Assertion messages must be strings
AVA now enforces assertion messages to be strings. The message is only used when the assertion fails, and non-string values may cause AVA to crash. You may see test failures if you were accidentally passing a non-string message. 49120aa
Flow type definitions
We've decided to remove the Flow type definitions from AVA itself. We don't have anybody to maintain them and consequently they've become a blocker when adding features to AVA. c633cf0
We've set up a new repository from which we'll publish the definitions, but we need your help setting it up. If you use AVA and Flow, please join us in #1.
Observable typing
Test implementations may return observables. We've updated our TypeScript definition to require these to have a
Symbol.observablefunction. c2d8218New features
Configurable printing depth
AVA now uses the
util.inspect.defaultOptions.depthoption when printing objects, so you can configure the depth. 98034fbSpecify environment variables in your AVA config
You can now specify environment variables in your config, using the
environmentVariablesobject. a53ea15Other changes
We've added
UntitledMacroandUntitledCbMacrotypes, for macro functions that will never have a.titlefunction. Though really this just helped simplify the type definition. Thanks @qlonik! ebf4807The dependency tracking in watch mode now respects custom require hooks you install in the worker processes. Thanks @lo1tuma! cb4c809
The TypeScript definition once again allows
test.skip(macro)ba5cd80AVA now exposes some methods to our ESLint plugin, allowing our plugin to support the new test & helper file selection. 51433be
All changes
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.x
1.4.1
27 Mar 2019Filtered tests (when using
--match,.skip()or.only()) are no longer included in the list of pending tests when timeouts occur or when you interrupt a test run. Thanks @vancouverwill! 23e302aWe're now shimming all TTY methods in the worker processes, thanks to @okyantoro. c1f6fdf
Focusing
power-assertAVA comes with
power-assertbuilt-in, giving you more descriptive assertion messages. However it's been confusing to understand which assertions come withpower-assert. To address this we've added the newt.assert()assertion. It's now the only assertion that ispower-assertenabled. The assertion passes if called with a truthy value. Consider this example:test('enhanced assertions', t => { const a = /foo/; const b = 'bar'; const c = 'baz'; t.assert(a.test(b) || b === c); });AVA will output: 6: const c = 'baz'; 7: t.assert(a.test(b) || b === c); 8: });
Value is not truthy:
false
a.test(b) || b === c
=> falseb === c
=> falsec
=> 'baz'b
=> 'bar'a.test(b)
=> falseb
=> 'bar'a
=> /foo/Our ESLint plugin has been updated to support this new assertion. Many thanks to @eemed for implementing this! 9406470
Watch mode
Watch mode now prints the available commands. Thanks @KompKK! cd256ac
Bug fixes
Filtered tests (when using
--match,.skip()or.only()) are no longer included in the list of pending tests when timeouts occur or when you interrupt a test run. Thanks @vancouverwill! 23e302aWe're now shimming all TTY methods in the worker processes, thanks to @okyantoro. c1f6fdf
All changes
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.4.0
24 Mar 20191.3.1
5 Mar 2019Snapshot files are now recognized as source files, so if you're using watch mode and you delete one, AVA won't rerun all your test files. d066f6f
Bug fixes
We've fixed a rather embarrasing bug with
t.throws()andt.throwsAsync(). If you'd set acodeexpectation to a number we never actually checked that the thrown error had such a code! Thanks to @qlonik for both spotting and fixing this. 82daa5e1.2.0 contained a regression which meant that if you faked
clearTimeout(), you'd break AVA. That's now been fixed. 40f331cSnapshot files are now recognized as source files, so if you're using watch mode and you delete one, AVA won't rerun all your test files. d066f6f
New features
You can now use
require()inava.config.jsfiles to load non-ES modules. 334e15bAll changes
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.3.0
5 Mar 20191.2.1
5 Feb 2019This is a bug fix release. In very large projects, the options send to worker processes would exceed limits on process argument size. We're now sending the options via the inter-process communication channel. 3078892
This is a bug fix release. In very large projects, the options send to worker processes would exceed limits on process argument size. We're now sending the options via the inter-process communication channel. 3078892
All changes
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.2.0
27 Jan 2019We're no longer truncating multi-line error messages 72e0762
Unexpected errors in the throws assertions are now reported with the correct stack trace ad087f2
The Debugging with VSCode recipe has been updated with the correct
workspaceFoldervariable 0a5fe42 and--serialargument placement edfc005
New features
You can now set a timeout for test themselves. The test will fail if this timeout is exceeded. The timeout is reset each time an assertion is made:
test('foo', t => { t.timeout(100); // 100 milliseconds // Write your assertions here });AVA also has a global timeout feature. The mini reporter now logs tests that were pending when those timeouts occur. Additionally, if you interrupt a test using ctrl+c we'll now also show the pending tests. 2b60556
Bug fixes and other improvements
We're no longer truncating multi-line error messages 72e0762
Unexpected errors in the throws assertions are now reported with the correct stack trace ad087f2
The Debugging with VSCode recipe has been updated with the correct
workspaceFoldervariable 0a5fe42 and--serialargument placement edfc005
All changes
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.1.0
13 Jan 2019t.log()now works in hooks d187712Error output for improper usage of
t.throws()once again links to the correct documentation dc552bcWe've added a section on webpack aliases to the Babel recipe c3bcbf2
New features
AVA now exports a
metaobject. 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 d187712Error output for improper usage of
t.throws()once again links to the correct documentation dc552bcWe'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
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.1
15 Dec 2018- Breaking
.serialmust be used at the beginning, e.g.test.serial(). - Breaking
.onlyand.skipmust be used at the end, e.g.test.skip(). You cannot combine them. - Breaking
.failingmust be used at the end, but can be followed by.onlyand.skip, e.g.test.cb.failing()andtest.cb.failing.only().
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.
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
messageshould be equal to it.If you pass a regular expression: the exception's
messageshould 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()andt.notThrows(). Use the newt.throwsAsync()andt.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()(ort.notThrows()). If you have a promise that should reject, or an asynchronous function that should fail, useawait t.throwsAsync()(orawait t.notThrowsAsync()).Generally speaking, you should be able to replace every occurence of
await t.throwswithawait t.throwsAsync, andawait t.notThrowswithawait 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.jsto 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()andt.log()are now also bound to the test.BigInt
As part of our Node.js 10 support you can now use
BigIntvalues int.deepEqual()andt.snapshot(). Note that this is still a stage-3 proposal.Babel 7
AVA now uses Babel 7, with support for
babel.config.jsfiles. We'll automatically use your project's Babel configuration. Babel options must now be specified in atestOptionsobject. This will allow us to add source related options in the future.Our
@ava/stage-4preset is now accessible viaava/stage-4. We've added transforms for the latest ES2018 features where available (and even an ES2019 one!). You can also disableava/stage-4entirely: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
powerAssertoption and command line flags have been removed. You can now disable AVA's test enhancements by settingcompileEnhancementstofalse. You can also disable AVA's Babel pipeline entirely:package.json:{ "ava": { "babel": false, "compileEnhancements": false } }Serial hooks and context
Hooks declared using
test.serialwill 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 usetest.serialto declare them.t.contextcan now be used in.beforeand.afterhooks.CLI
Pass flags to your test
AVA now forwards arguments, provided after an
--argument terminator, to the worker processes. Arguments are available fromprocess.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]andprocess.argv[3]with some undocumented internal values. These are no longer available.Resetting AVA's cache
The
--no-cacheCLI flag has been replaced by a--reset-cachecommand. The latter resets AVA's regular cache location. You can still disable the cache through thecacheconfiguration option.npx ava --reset-cache
Configuration
Introducing
ava.config.jsYou can now configure AVA through an
ava.config.jsfile. It must be placed next to thepackage.json, and you mustn't have any"ava"options in thepackage.jsonfile. 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 specifybabel.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
BigIntand<React.Fragment>int.snapshot(). We've also improved support for theSymbol.asyncIteratorwell-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
tscbefore 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.Type definitions
The TypeScript and Flow definitions have been rewritten and much improved. The TypeScript recipe has been updated to reflect the changes, and there's a new Flow recipe too.
TypeScript
AVA recognizes TypeScript build errors when using
ts-node/register.TypeScript now type-checks additional arguments used by macros. You must type the arguments used:
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 compileOther improvements
You can now specify helpers — that need to be compiled by AVA — in the
requireconfiguration.--fail-fastbehavior has been improved. AVA now makes sure not to start new tests. Tests that are already running though will finish. Hooks will also be called. AVA now prints the number of skipped test files if an error occurs and--fail-fastis enabled.AVA now uses its own Chalk instance, so AVA's color settings no longer impact the code you're testing.
Error serialization has been made smarter, especially if non-Error errors are encountered.
Uncaught exceptions and unhandled rejections are now shown with a code excerpt.
You should see fewer repeated test timeout messages.
Error messages now link to the documentation appropriate for the version of AVA you're using.
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-varspackage for a list of supported CI environments.AVA now detects when it's required from a Node.js REPL.
We've improved the colors for use on light terminal themes.
The
assertmodule in Node.js 10 no longer crashes.Source maps, generated by AVA when compiling test & helper files, now contain correct paths to the source files.
TTY support for
process.stderris now emulated in the worker processes.The default reporter now includes files that did not declare any tests in its final output.
AVA now prints pending tests when timeouts occur, when using
--verbose.<React.Fragment>can be used int.deepEqual.titlefunctions of macros now receiveundefinedrather than an empty string if no title was given in the test declaration. This means you can use default parameters.
Breaking changes since 0.25.0
Supported Node.js versions
We've published a statement with regards to which Node.js versions we intend to support. As of this release we're only supporting Node.js 6.12.3 or newer, 8.9.4 or newer, 10.0.0 or newer and 11.0.0 or newer. This does not include Node.js 7 and 9.
Tests must now have titles, and they must be unique
You can no longer do:
test(t => t.pass());
Instead all tests must have titles, and they must be unique within the test file:
test('passes', t => t.pass());This makes it easier to pinpoint test failures and makes snapshots better too.
Note that AVA no longer infers a test title from a function name:
test(function myTest (t) { t.pass(); });Modifier chaining
AVA's various test modifiers (
.serial,.skip) must now be used in the correct order:- Breaking
.serialmust be used at the beginning, e.g.test.serial(). - Breaking
.onlyand.skipmust be used at the end, e.g.test.skip(). You cannot combine them. - Breaking
.failingmust be used at the end, but can be followed by.onlyand.skip, e.g.test.cb.failing()andtest.cb.failing.only(). - Breaking
.alwayscan only be used after.afterand.afterEach, e.g.test.after.always(). - Breaking
.todo()is only available ontestandtest.serial. No further modifiers can be applied.
Declaring tests
You must declare all tests and hooks at once. This was always the intent but previously AVA didn't enforce it very well. Now, once you declare a test or hook, all other tests and hooks must be declared synchronously. However you can perform some asynchronous actions before declaring your tests and hooks.
testexportWe're no longer exporting the
test()method as a named export. Where before you could useimport {test} from 'ava', you should now writeimport test from 'ava'.Set default title using parameters syntax
Macros can generate a test title. Previously, AVA would call the
titlefunction with an empty string if no title was given in the test declaration. Now, it'll passundefinedinstead. 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.
Assertions
t.throws()&t.notThrows()Thrown exceptions (or rejection reasons) must now be error objects.
t.throws()andt.notThrows()no longer support observables or promises. For the latter, useawait t.throwsAsync()andawait t.notThrowsAsync()instead.Generally speaking, you should be able to replace every occurence of
await t.throwswithawait t.throwsAsync, andawait t.notThrowswithawait 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.jsto a glob pattern that matches your test files. See the jscodeshift CLI usage documentation for further details.Skipping assertions
Assertions can be skipped by using
.skipat the end of the assertion, e.g.t.deepEqual.skip(). You can now safely skip snapshot tests, though not whilst updating snapshots.t.ifError()We've removed the
t.ifError()assertion. It worked the same ast.falsy(), so if you were using it please switch tot.falsy()instead.Configuration changes
The
sourceoption has been renamed tosources. This is now consistent withfiles. AVA will exit with an error if it encounters thesourceoption.We've also removed unintentional support for
init,watchandupdateSnapshotoptions.Babel
The
"default"and"inherit"configuration values have been removed. Babel options must now be specified in atestOptionsobject. This will allow us to add source related options in the future.The
powerAssertoption and command line flags have been removed. You can now disable AVA's test enhancements by settingcompileEnhancementstofalse.The Babel recipe has been updated with the latest details.
Updated type definitions
The TypeScript and Flow definitions have been rewritten. The definitions export different interfaces so you may need to update your test code as well.
TypeScript now type-checks additional arguments used by macros. You must type the arguments used.
Internals
Some other internals have changed. You shouldn't have been relying on these, though if you did we're interested in hearing about it so we can better support your use case.
- Breaking
The private
t._testvalue has been removed - Breaking
Some of the communication between the main process and the test workers has changed
- Breaking
Access to the options object from inside a worker process has changed
Other potential breaking changes
- Breaking
We've removed support for
@std/esm, in favor of the plainesmpackage. - Breaking
The
ava/stage-4preset is applied after all other plugins and presets. - Breaking
Test implementations are now called with
nullas thethisvalue. - Breaking
All reporters write to
stdout. Thestdoutandstderroutput from workers is written toprocess.stderr. AVA will insert linebreaks inprocess.stdoutafter writing a chunk toprocess.stderrthat does not end in a line break. - Breaking
The
--no-cacheCLI flag has been replaced by a--reset-cachecommand. The latter resets AVA's regular cache location. You can still disable the cache through thecacheconfiguration option. - Breaking
We've dropped support for using generator functions as test implementations. This was a remnant of the dark days before
async/awaitsupport. - Breaking
Snapshots need to be regenerated.
- Breaking
If you pre-compile your test files, the snapshot files may be created at new file paths. You'll have to manually remove any old files.
New recipes
There's a new recipe on using ES modules. We've also added a recipe on setting up tests and how test webapps using AVA and Puppeteer.
All changes
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
14 Apr 2016- 0.25.x
0.25.0
26 Jan 2018t.log()now supports multiple arguments 4f896c2AVA no longer globally modifies
Error.stackTraceLimitin the worker processes f00f3c4
Another small release while we're gearing up for a 1.0 built with Babel 7. This is likely to be the last
0.release, but we may go through a few beta releases for 1.0 whilst we wait for Babel 7 to get out of beta itself.We now detect
@std/esmin AVA's"require"configuration and will use it to require subsequent modules 72c53bet.log()now supports multiple arguments 4f896c2AVA no longer globally modifies
Error.stackTraceLimitin the worker processes f00f3c4We've improved TypeScript typings for
t.snapshot(value, options)29e5dfdSource maps for the test files can now be resolved if they reside on a different drive aaddc37
Code excerpts shown for test failures now handle Windows-style linebreaks 947f207
We've updated the Debugging tests with Visual Studio Code recipe with tips on serial debugging and skipping dependencies 4a13966 bcb77fc
All changes
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.
- 0.24.x
0.24.0
27 Nov 2017This is a pretty small release, but a great one if you're solely developing for Node.js 8.3 or above.
Highlights
This is a pretty small release, but a great one if you're solely developing for Node.js 8.3 or above.
You can now use object rest/spread properties in test files without any further Babel configuration. Note that if you're running tests on older versions of Node.js you'll still need to add the relevant Babel plugins, since this new language feature has not yet reached stage 4. 37c9122
All changes
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.
- 0.23.x
0.23.0
24 Oct 2017AVA will now set
process.env.NODE_ENVto'test', as long as theNODE_ENVenvironment variable has not already been set. 42e7c74Highlights
NODE_ENV=testAVA will now set
process.env.NODE_ENVto'test', as long as theNODE_ENVenvironment variable has not already been set. 42e7c74Improved snapshot storage location
Snapshots are stored alongside your test files. This is great when your test file is executed directly but say if you're using TypeScript to precompile your test file AVA would store the snapshots in your build directory. In this release, if source maps are available, AVA determines the original test file location and uses that to store the snapshots.
You can also specify where snapshots are stored through the
snapshotDiroption in thepackage.jsonfile. 7fadc34Matching anonymous tests
--match='*'now matches all tests, including those without a title. 1df502dAll changes
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.
- 0.22.x
0.22.0
15 Aug 2017The WebStorm recipe has been updated with instructions on how to enable the Node.js inspector. d8c21a6
The app setup in the endpoint testing recipe has been fixed e28be05
The
t.notThrows()example has been clarified 57f5007
There's but a few commits in this release, but we've made a big change to how AVA manages its test workers 👩🏼🔬👨🏼🏭👨🏿🚀👨🏻⚕️👩🏽💼.
Highlights
Default concurrency
We now cap the number of concurrent workers to the number of CPU cores on your machine. Previously AVA started workers for each test file, so if you had many test files this could actually bring things to a halt. 465fcec
You can still customize the concurrency by setting the
concurrencyoption in AVA'spackage.jsonconfiguration, or by passing the--concurrencyflag. We've also beefed up input validation on that flag. b6eef5aUnfortunately this does change how
test.only()behaves. AVA can no longer guarantee that normal tests won't run. For now, if you want to usetest.only(), you should run tests from just that file. We have an open issue to add an--onlyflag, which will ensure that AVA runs just thetest.only()tests. If you'd like to help us with that please head on over to #1472.t.log()We've also added
t.log(), which lets you print a log message contextually alongside the test result, instead of immediately printing it tostdoutlikeconsole.log. 14f7095Miscellaneous
The WebStorm recipe has been updated with instructions on how to enable the Node.js inspector. d8c21a6
The app setup in the endpoint testing recipe has been fixed e28be05
The
t.notThrows()example has been clarified 57f5007
All changes
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.
- 0.21.x
0.21.0
13 Jul 2017Additional arguments can be passed when profiling 05bfafe
Though not officially supported, AVA now works better with Wallaby.js’ diff view 3f6e134
Expanded the Webstorm recipe to include setup instructions using
npm2b4e35d
This is primarily a bug fix release, but some features did sneak in:
Additional arguments can be passed when profiling 05bfafe
Though not officially supported, AVA now works better with Wallaby.js’ diff view 3f6e134
Expanded the Webstorm recipe to include setup instructions using
npm2b4e35d
This release includes the following patches:
Fixes for
t.deepEqual()and magic assert diffs 9e4ee3fEnsure AVA doesn’t use
BufferAPIs that are unavailable in Node.js releases older than 4.5 d0fc8c9Changed Flow typing of the
t.throws()promise return value to beany4a769f8Update Flow typing of
test()so macros are compatible with the latestflow-bine794e73
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.
- 0.20.x
0.20.0
28 Jun 2017Argumentobjects can only be compared toArgumentobjectsFunctions are compared by name and other enumerable properties
Promises are compared by their constructor and additional enumerable properties
Today’s release is very exciting. After adding magic assert and snapshot testing we found that these features sometimes disagreed with each other.
t.deepEqual()would returnfalse, yet AVA wouldn’t show a diff. Snapshot tests cared aboutSetorder butt.deepEqual()didn’t. @novemberborn came to the realization that comparing and diffing object trees, and doing so over time with snapshots, are variations on the same problem. Thus he started ConcordanceJS, a new project that lets you compare, format, diff and serialize any JavaScript value. This AVA release reaps the fruits of his labor.Highlights
More magical asserts
Magic assert will now always show the difference between actual and expected values. If an unexpected error occurs it’ll print all (enumerable) properties of the error which can make it easier to debug your program.
Example of a formatted exception
More details of an object are printed, like the constructor name and the string tag. Buffers are hex-encoded with line breaks so they’re easy to read:
Example of diffed Buffers
t.deepEqual()improvementst.deepEqual()andt.notDeepEqual()now useconcordance, rather thanlodash.isequal. This changes what values AVA considers to be equal, making thet.deepEqual()assertion more predictable. You can now trust that all aspects of your objects are compared.Object wrappers are no longer equal. The following assertion will now fail:
t.deepEqual(Object(1), 1); // fails
For
MapandSetobjects to be equal, their elements must now be in the same order:const actual = new Set(['hello', 'world']); t.deepEqual(actual, new Set(['hello', 'world'])); // passes t.deepEqual(actual, new Set(['world', 'hello']) // fails
With this release AVA will compare all enumerable properties of an object. For an array this means that the comparison considers not just the array elements. The following are no longer considered equal:
const actual = [1, 2, 3]; const expected = [1, 2, 3]; expected.also = 'a property'; t.deepEqual(actual, expected); // fails
The same goes for
MapandSetobjects, errors, and so forth:const actual = new TypeError('Bad value'); const expected = new TypeError('Bad value'); expected.value = 41; t.deepEqual(actual, expected); // failsYou used to be able to compare
Argumentsobject to an object literal:const args = (function() { return arguments; })('hello', 'world'); t.deepEqual(args, {0: 'hello', 1: 'world'}); // now failsInstead you must now use:
const args = (function() { return arguments; })('hello', 'world'); t.deepEqual(args, ['hello', 'world']); // passes(Of course you can still compare
Argumentsobjects to each other.)New in this release is the ability to compare React elements:
t.deepEqual(<HelloWorld/>, <HelloWorld/>); const renderer = require('react-test-renderer'); t.deepEqual(renderer.create(<HelloWorld/>).toJSON(), <h1>Hello World</h1>);Snapshot improvements
Snapshots too now use
concordance. This means values are compared with the snapshot according to the same rules ast.deepEqual(), albeit with some minor differences:Argumentobjects can only be compared toArgumentobjectsFunctions are compared by name and other enumerable properties
Promises are compared by their constructor and additional enumerable properties
Symbols are compared by their string serialization. Registered and well-known symbols will never equal symbols with similar descriptions
Note that Node.js versions before 6.5 cannot infer names of all functions . AVA will pass a snapshot assertion if it determines the name information is unreliable.
AVA now saves two files when snapshotting. One, ending in the
.snapextension, contains a compressed serialization of the expected value. The other is a readable Markdown file that contains the snapshot report. You should commit both to source control. The report file can be used to see what is in your snapshots and to compare snapshot changes over time.Try it out with our snapshot example! Or check out an example snapshot report.
The snapshot file location now follows your test layout. If you use a
testfolder, they’ll be placed intest/snapshots. With__tests__they’ll be placed in__tests__/__snapshots__. And if you just have atest.jsin your project root the snapshot files will be written totest.js.snapandtest.js.md. You may have to manually remove old snapshot files after installing this new AVA version. ebd572aImproved snapshot support in watch mode
In watch mode, AVA now watches for changes to snapshot files. This is handy when you revert changes while the watcher is running. Snapshot files are correctly tracked as test dependencies, so the right tests are rerun. Typing
u, followed byEnterupdates the snapshots in the tests that just ran. (And the watcher won’t rerun tests when snapshots are updated.) 87eef84 dbc78dc f507e36 50b60a1Node.js 8 support
AVA 0.19 already worked great with Node.js 8, and we’ve made it even better by removing unnecessary Babel transpilations in our
stage-4preset. We’re now also forwarding the--inspect-brkflag for debugging purposes. e456951 a868b02New and improved recipes
We’ve added new recipes and improved others:
Learn how to debug tests with Visual Studio Code 1d04153 140c0e0
There’s several ways of using webpack to precompile tests and sources. We’ve broken down the pros and cons f228401
We’ve added a note to the browser testing recipe, discouraging the use of
browser-envc01ac05
Miscellaneous
Specifying
--concurrencywithout a value now causes AVA to exit with an error 8c35a1aUsing
t.throws()with a resolved promise now prints a helpful error message dfca2d9The
t.titleaccessor has been documented. 549e99b
All changes
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.
- 0.19.x
0.19.1
10 Apr 2017Prevent
MaxListenersExceededWarningfrom being emitted if a test file contains more than 10 tests d27bc8fFix
t.end()not being available in the TypeScript definition for callback tests bd81ef4Fix
t.contextnot being available in the Flow definition forbeforeEach()andafterEach()hooks d169f0e
A bugfix release. See
0.19.0for full release notes.0.19.0
5 Apr 2017You can now type the test context when using TypeScript. 50ad213
The color of text diff output has been fixed. 9f2ff09
Since our last minor release, @novemberborn has worked tirelessly on refactoring big parts of the codebase to be more correct and readable, while squashing many bugs. We've also added multiple detections that will prevent user mistakes.
Highlights
Working snapshots
We released snapshot support with
v0.18.0, but unfortunately it didn’t work. That’s fixed now. Since we’re usingjest-snapshotthe output will look a little different from AVA’s other assertions. Most notably the output will not be colored.Tests fail if no assertions are run (BREAKING)
Sometimes you write a test that accidentally passes, because your assertion was never run. For example, the following test passes if
getAnimals()returns an empty array:test('unicorn', t => { for (const animal of getAnimals()) { t.is(animal, 'unicorn'); } });AVA now fails your test if no assertions were run. This can be a problem if you use third-party assertion libraries, since AVA cannot detect when those assertions pass. You can disable this behavior by setting the
failWithoutAssertionsoption tofalsein AVA'spackage.jsonconfiguration.Improved
t.throws()andt.notThrows()assertions (BREAKING)Various improvements have been made to these assertions. Unfortunately this does include some breaking changes.
Calling these assertions with an observable or promise makes them asynchronous. You now need to
awaitthem:const promise = Promise.reject(new TypeError('🦄')); test('rejects', async t => { await t.throws(promise); });Previously, these would return a promise that was rejected if the assertion failed. This leaked AVA’s internal assertion error. Now they’ll fulfill their returned promise with
undefinedinstead (d56db75). You typically won’t notice this in your test.We’ve improved how we detect when
t.throws()andt.notThrows()are used incorrectly (d924045). This might be when, rather than passing a function, you call it:test('throws', t => { t.throws(throwingFunction()); });You can now use
awaitandyieldin the argument expressions (e.g.t.throws(await createThrowingFunction()). The instructions on how to use these assertions correctly are now shown with the test failure, instead of being written to the console as your tests run.Incorrectly using these assertions now always causes your test to fail.
Stack traces are now correct, even if used asynchronously (f6a42ba). The error messages have been improved for when
t.throws()fails to encounter an error, or ift.notThrows()does (4463f38). Ift.notThrows()fails, the encountered error is shown (22c93ed).Improved magic assert output
Actual and/or expected values are now included in the magic assert output, with helpful labels that are relevant to the failing assertion.
Detect hanging tests
AVA can now detect when an asynchronous test is hanging (880e87e).
Note that this may not work if your code is listening on a socket or is using a timer or interval.
Better Babel option resolution
We’re now resolving Babel options ahead of time, using
hullabaloo-config-manager. This fixes long-standing issues with relative paths in AVA’s"babel"options inpackage.jsonfiles (#707). It also means we’re better at recompiling test and helper files if your Babel config changes or you update plugins or presets.Miscellaneous
There is a new recipe for precompiling source files with webpack. a49f66b
You can now type the test context when using TypeScript. 50ad213
The color of text diff output has been fixed. 9f2ff09
Text diffs are now faster. bd5ed60
Values are no longer highlighted if colors are disabled. b581983
AVA no longer crashes if tests fail with non-errors. 157ef25
YAML blocks in the TAP output have been improved. 3279336
We’re now printing assertion statements with less depth. 0510d80
Arguments to
t.regex()andt.notRegex()are now validated. f062981
All changes
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.
- 0.18.x
0.18.2
18 Feb 2017Many bug fixes for snapshot testing, magic assert, and the type definitions: v0.18.1...v0.18.2
0.18.1
3 Feb 2017Quick bug fix: Remove
t.isandt.notfrom enhanced assertion patterns to provide correct output on assertion failure.0.18.0
2 Feb 2017- Removed
Removed the
--sourceflag. Use the package.json config instead. 34bebc4 Support symlinked test files. 033d4dc
This release is one of the biggest, most feature-packed release we’ve had in a long time. We have prepared lots of tasty things for you - snapshot testing, magic assert, precompiling test helpers, improvements to Babel transpilation, and more. Our team and contributors have been working hard to deliver all this goodness. We can’t wait to hear your feedback and don’t hesitate to suggest new ideas and report bugs!
Highlights
Dropped support for Node.js 0.10 and 0.12
As mentioned in the 0.17.0 release notes, we’re dropping support for Node.js 0.10 and 0.12 in this release. They’re both out of maintenance mode. Time to upgrade!
Magic assert
magic-assert-combined2
We completely overhauled the error output to make it as easy and fast as possible to detect the source of the failure. Magic assert, as we call it internally, adds code excerpts and clean diffs for actual and expected values. If values in the assertion are objects or arrays, only a difference is displayed to remove the noise and focus on the problem. Oh, and the diff is syntax-highlighted too! If you are comparing strings, both single and multi line, AVA displays a different kind of output, highlighting the added or missing characters. Last but not least, you don’t have to update any of your tests to take advantage of this! Third-party assertion libraries, like expect, chai and others, are supported out-of-the-box as well.
Snapshot testing
We now have snapshot testing, thanks to @lithin ✨
snapshot-testing
Snapshot testing simply saves a stringified state of some data structure and compares it on the next run. It was popularized with React component testing, but you can use it with anything that can be stringified. For example, ensuring API responses stay the same.
ee65b6dPrecompile helper files
Previously, AVA transpiled your test files, but not your test helpers. Now we transpile helper files too! Helpers are files starting with
_or any files in ahelpersdirectory inside the test directory. These are usually used for utilities and shared logic between test files.
410cb8dImproving language support
We’ve come up with a specification for how AVA handles Babel projects and may better support other languages like TypeScript. Customizing transpilation of test and helper files will be easier, and AVA will start transpiling source files too. We’ve started work on this, but there are no user-facing changes yet.
076eb81Miscellaneous
- Removed
Removed deprecated assertions (
t.ok,t.notOk,t.same,t.notSame). If you haven’t migrated yet, you can do so automagically with our codemod. c010fd7 - Removed
Removed the
--sourceflag. Use the package.json config instead. 34bebc4 Support symlinked test files. 033d4dc
No longer using
babel-runtime. Built-ins likeMapandPromiseare no longer replaced with polyfills. ad5122dPrints a warning when
test.only()is used, so you don’t mistakenly think you’re running all the tests. 22a6081Prints a warning when
--fail-fastis enabled, so you’re aware AVA didn’t run all your tests. 09d23f5Exits with an error when
--watchis used in CI, as otherwise the process would never exit, since watch mode is persistent. 0606ff7Only transpile what’s needed on Node.js 6. We already did that for Node.js 4. 5158ac8
TypeScript type definition improvement: 0603edc
All changes
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.
- 0.17.x
0.17.0
17 Nov 2016- Removed
Removed the
--requireCLI flag. Configure it in package.json instead. 17119bc - Deprecated
Deprecated
t.error()alias fort.ifError(). It will be removed in AVA 1.0.0. Just uset.ifError(). 28bb0d5 (We have an automatic migration script if you're usingt.error())
The current working directory in test files changed (BREAKING)
We made the hard decision of changing the current working directory (
process.cwd()) in test files to be the same directory aspackage.json. It was previously the same as__dirname(the directory of the test file). Havingprocess.cwd()equal__dirnamefelt like a good idea at the time, but as the popularity of AVA grew, people started hitting issues with it.This affects users that have test files in a sub-folder and are using relative paths. If you have your test files in the same directory as
package.json, you're fine.The fix is to wrap all relative paths in
path.join(__dirname, 'relative-path')to make them absolute.Here's an example of what needs changing. The below file and
unicorn.txtare both in./test/.-t.true(fs.existsSync('unicorn.txt')); +t.true(fs.existsSync(path.join(__dirname, 'unicorn.txt')));Let us know if anything is unclear or if you're having problems.
Commit: 476c653
Node.js version support
The next minor version of AVA, 0.18.0, will drop support for Node.js v0.10 and v0.12. We'll continue fixing critical issues for this version until the end of the year. Time to upgrade if you haven't. (Discussion: #1051)
Highlights
We now have a script to automatically migrate from tape to AVA.
Our ESLint plugin received two new rules:
Reduced transpilation on Node.js >=4. AVA now only transpiles what's needed for Node.js 4 when on it or higher, which should result in better performance and stacktraces. 4025d81
- Removed
Removed the
--requireCLI flag. Configure it in package.json instead. 17119bc Switched to
lodash.isEqualfor deep equality checking (t.deepEqual()&t.notDeepEqual()). This might make your test fail if our previous deep equality check was too loose. 8856684Improvements to the test failure output. e4f90e0 (We're currently working on many more improvements in this area. Stay tuned.)
Added option to disable
power-assert. 24a38acCorrectly clean up stacktraces on Node.js 6 and higher. 26bcab0
Removed
t.doesNotThrow()as it was renamed tot.notThrows(). It was deprecated far back in AVA 0.12.0. e448798- Deprecated
Deprecated
t.error()alias fort.ifError(). It will be removed in AVA 1.0.0. Just uset.ifError(). 28bb0d5 (We have an automatic migration script if you're usingt.error()) Ensures test files load correct AVA installation. This means you can now run AVA with an absolute path and it will still use the local AVA installation at that path if available. 3ea2ba1
Added support for debugging tests with WebStorm and added a recipe. c268c8d
Improvements to the TypeScript type definition. 4baa170 8816faf c40477a
We started exploring browser support. 204f2be
All Changes
- 0.16.x
0.16.0
6 Aug 2016Add
t.notRegex(). c740202Provide clear error message when users attempt nested or async calls to
test(). 8edd9c2
Hope you all are having a great summer! 😎
Highlights
Add
t.notRegex(). c740202Provide clear error message when users attempt nested or async calls to
test(). 8edd9c2Document common pitfalls when using AVA. 187b8b4
All Changes
- 0.15.x
0.15.2
4 Jun 2016Avoids deprecation warning from
loud-rejection.0.15.0
25 May 2016Improve
t.deepEqual(). 973624dImprove watch logging. 95a5c97
Disable TAP-reporter in watch mode. 02b0aae
In this release we've added some very useful features we think you'll like. There are no known breaking changes. We have worked hard on fixing bugs and improving performance. Going forward stability and performance will be our top priority as we're progressing towards a stable release. Finally, we're delighted to welcome @sotojuan to the team! 🎉
Test file conventions
When you run AVA without any arguments, it tries to find your test files based on some conventions. The previous release had the following default patterns:
test.js test-*.js test/**/*.js
In this release we added additional default patterns based on community conventions:
test.js test-*.js test/**/*.js **/__tests__/**/*.js **/*.test.js
This means AVA will now also run test files in
__tests__directories and test files ending in.test.jsanywhere in your project.Known failing tests
A big part of open source maintenance is triaging issues. This can be a tedious task, involving a lot of back and forth with the person reporting the issue. Submitting a PR with a failing test makes the whole process much more efficient. It helps maintainers by providing a quality reproduction, allowing them to focus on code over triaging. Users benefit as their bugs get fixed faster.
To make it easier to submit failing tests, we're introducing a new test modifier:
test.failing(). These tests are run just like normal ones, but they are expected to fail, and will not break your build when they do. If a test marked as failing actually passes, the build will break with a helpful message instructing you to remove the.failingmodifier.test.failing('demonstrate some bug', t => { t.fail(); // test will count as passed });This allows you to merge
.failingtests before a fix is implemented without breaking CI. It is also a great way to recognize good bug reports with a commit credit, even if the reporter is unable to fix the problem.Test macros
Sometimes you want to run a series of very similar tests, each with different inputs and expected results. The traditional solution is to use test generator functions. However, this makes it difficult to perform static analysis on the tests, which is especially important for linting. In this release, we are introducing test macros as the official way to create reusable tests.
Test macros let you reuse test implementations. Additional arguments passed in the test declaration are forwarded to the macro:
function macro(t, input, expected) { t.is(eval(input), expected); } test('2 + 2 === 4', macro, '2 + 2', 4); test('2 * 3 === 6', macro, '2 * 3', 6);If you are generating lots of tests from a single macro, you may want to generate the test title programmatically:
macro.title = (providedTitle, input, expected) => { return `${input} === ${expected}` };Always modifiers for after and afterEach hooks
By default
afterandafterEachhooks will not be run if the preceding test fails. This is undesirable if the hooks contain cleanup code that you want run regardless. You can change that behavior using the.alwayschaining modifier.test.after.always(t => { // always runs at the end. Regardless of test pass/fail state. }); test.afterEach.always(t => { // always runs after each test. Regardless of test pass/fail state. });Note that the
--fail-fastswitch will disable this behavior, and AVA will exit at the first encountered failure without waiting for thealwayshooks.Limited concurrency [EXPERIMENTAL]
Concurrency is awesome! It's what makes AVA so fast. Our default behavior is to spin up an isolated process for every test file immediately, and then run all your tests. However, for users with lots of test files, this was eating up too many system resources, causing memory and IO thrashing. We are experimenting with an option to let you limit how many tests files AVA runs at the same time. If you have a lot of test files, try running AVA with the
--concurrencyflag. For example, run$ ava --concurrency=5and see if the performance improves. Please let us know how it works for you! We need feedback on the feature.Note: This is an experimental feature and might change or be removed in the future.
Highlights
Improve
t.deepEqual(). 973624dImprove watch logging. 95a5c97
Disable TAP-reporter in watch mode. 02b0aae
Throwing synchronously inside a callback-style test now fail it immediately. d6acdde
Detect improper use of
t.throws. 3201b1bProtect against bad argument passed to
t.throws. 60bd8a5Improve
power-assertoutput. 84c05feAdd spinner fallback for Windows. c4e58e3
Warn about
npm linkusage on Node.js 6. a543b9fRemember failures from previous tests in watch mode. aab2207
Fix crash in 'fake' browser environment. 0fa229e
Fix warning when no files are found. ee76aa9
Strip ANSI escape codes in the TAP output. 3c4babd
React recipe. 4c69c79
Italian translation of the docs. 195390e
All Changes
We’ve merged 92 commits from 23 contributors since
0.14.0. This only scratches the surface, as lots of additional work has gone into our linter, localized docs and countless other projects that make AVA possible. To everyone who’s reported bugs, contributed to design discussions, and filed PR’s with documentation or code - Thank You!- 0.14.x
0.14.0
7 Apr 2016- Deprecated
A number of assertion methods have been renamed for clarity. The old methods still exist, but have been deprecated, and will be removed in a future release (e9c6cc2, a7f50eb). We have published
ava-codemodsto assist in automatically renaming these assertions in your tests. Added an idle timeout option to prevent test runs from hanging indefinitely. The test run is considered timed out when no test results have been received for the specified interval. d1a3669
Published a recipe on various ways to configure Babel. bcda753
The biggest change in this release is the deprecation of
t.ok,t.notOk,t.same, andt.notSameassertions. We have published a codemod (automatic migration script) which should make switching to the new assertion methods very easy.Also, we've added a
--timeoutflag that will stop test execution after a certain period of inactivity.Highlights
- Deprecated
A number of assertion methods have been renamed for clarity. The old methods still exist, but have been deprecated, and will be removed in a future release (e9c6cc2, a7f50eb). We have published
ava-codemodsto assist in automatically renaming these assertions in your tests.t.ok()→t.truthy()t.notOk()→t.falsy()t.same()→t.deepEqual()t.notSame()→t.notDeepEqual()
Added an idle timeout option to prevent test runs from hanging indefinitely. The test run is considered timed out when no test results have been received for the specified interval. d1a3669
Published a recipe on various ways to configure Babel. bcda753
Updated Russian, Chinese, and Spanish translations. Big thanks to our translation team!
Of Note
t.deepEqual()(formerlyt.same()) no longer compares constructors. a7826cfTruncate test titles in the mini reporter. 6d5f322
Fix
t.throws()not returning error for synchronous methods. 26d2291Now throws a meaningful error if
--requiredependency is not found. c78e736Watch mode will now rerun all
.onlytests regardless of dependency graph. e57908aPrint the planned and actual assertion count when there is a plan failure. 07febb2
Workaround for Node.js bug which could kill main process. cd6961a
Mini reporter no longer flashes test titles for
skip/todotests. ecc87cbDisplay a helpful error message for invalid Babel config. febbaa2
Switch from
serialize-errortoclean-yaml-object(better compatibility withnode-tap). cd5767eRewrite
require("babel-runtime")in tests to absolute path (allows module resolution fornpm@2without modifyingNODE_PATHS). 382e50dEnsure source maps can be resolved from cached code. 592ff13
Produces a helpful failure method when users incorrectly provide an implementation method to
test.todo(). 8d6490a
All Changes
Shout-out to @kentcdodds @sotojuan @SamVerschueren @mattkrick for their awesome contributions to this release! ✨🎉
- 0.13.x
0.13.0
10 Mar 2016Added support for Babel config in the
avaconfig package.json. This will let you configure AVA to use your own Babel config (.babelrc orbabelin package.json). a03f826Added intelligent watch mode. f0f4f34
Added
todotest modifier. e697629
The most exciting changes in this release are support for using your own Babel config with AVA and an intelligent watch mode that watches for test and source changes and runs only tests that are affected.
We now have an awesome list. Our ESLint plugin got some new rules. And @novemberborn is a team member!
Highlights
Added support for Babel config in the
avaconfig package.json. This will let you configure AVA to use your own Babel config (.babelrc orbabelin package.json). a03f826Added intelligent watch mode. f0f4f34
Added
todotest modifier. e697629Added ability to run only tests with matching titles. c928cb5
t.throws()now returns error or rejection reason of promise. e03b82cDon't coerce non-Error promise rejection to an error. 5e02387
test.only()now works across all test files. 6b1617aFixed AVA hanging when
testis used incorrectly. 94c03f6Added TypeScript typings. 0e18865
Added TypeScript recipe. 20c66fe
Added browser testing recipe. 2f10448
Changes
- 0.12.x
0.12.0
18 Feb 2016- Breaking
****
t.doesNotThrow()is renamed tot.notThrows()to be consistent with the other assert methods.t.doesNotThrow()will be removed in AVA 1.0.0. a35d130 [maybe breaking] We removed the undocumented
t.regexTest()assert method and addedt.regex().t.regexTest()had the wrong argument order.t.regex()follows the same argument order as other assert methods. a10b9e8
This release is mostly focused on improving performance and doing some hopefully final breaking changes. We've also started work on an ESLint plugin and editor plugins for AVA, where we could use some help and feedback.
Highlights
- Breaking
****
t.doesNotThrow()is renamed tot.notThrows()to be consistent with the other assert methods.t.doesNotThrow()will be removed in AVA 1.0.0. a35d130 [maybe breaking] We removed the undocumented
t.regexTest()assert method and addedt.regex().t.regexTest()had the wrong argument order.t.regex()follows the same argument order as other assert methods. a10b9e8More performance improvements! (∩`-´)⊃━☆゚.*・。゚ e010816 341c84b 9b0d5f7
Add recipe "When to use
t.plan()". 39982a5Improve error determination, which fixes some issues with the output when non-errors or errors without a message are thrown. #555
Support
NODE_PATH(Please don't useNODE_PATHunless you really have to!) 0675d34
Changes
- 0.11.x
0.11.0
23 Jan 2016- 0.10.x
0.10.0
15 Jan 2016- Breaking
.babelrcfiles will now be ignored when transpiling tests. This will be a breaking change for some, and fix major problems for others. The ability to configure test transpilation will be restored in a future update. 5f5be31 New Spanish translation of the documentation. 37cd685
Started a collection of
recipesfor common scenarios / best practices. 4d96a3e
Highlights
Customize the default behavior in
package.jsonAll of the CLI options can be configured in the AVA section of your package.json. This allows you to modify the default behavior of the AVA command, so you don't have to repeatedly type the same options on the command prompt.
{ "ava": { "files": [ "my-test-folder/*.js", "!**/not-this-file.js" ], "failFast": true, "serial": true, "tap": true, "verbose": true, "require": ["babel-core/register", "coffee-script/register"] } }Clean stack traces
Unrelated lines are now removed from stack traces, allowing you to find the source of an error much faster.
Improved performance
Babel transpilation of test files now happens in the main process. This avoids requiring Babel in every child process and greatly improves performance. This is an especially important improvement for people still running
npm@2.New
power-assertupdates reduce the size of it's dependency graph. Offering improvements to both download times and performance.Clean
console.logoutput.The test status output and
console.logstatements from within your own code will no longer interfere with each other. The test status remains fixed at the bottom of the output.Other Changes
New Spanish translation of the documentation. 37cd685
Started a collection of
recipesfor common scenarios / best practices. 4d96a3eAll assertion methods now return a promise. 821436a
Long stack traces are turned on in forked processes. da6a2f4
Skippable assertions are now documented. 879e036
- Breaking
.babelrcfiles will now be ignored when transpiling tests. This will be a breaking change for some, and fix major problems for others. The ability to configure test transpilation will be restored in a future update. 5f5be31 Added a Code of Conduct b76f3d5
Changes
- 0.9.x
0.9.0
29 Dec 2015- Breaking
Deeply recurse directories. Previously AVA only looked for test files in the immediate subdirectory. Now it will look in subdirectories at any level. 72e87d9
Ignore files in directories named
fixturesandhelpers. f6cef7fCache Babel transpiled code. This will improve startup performance considerably. 0daec3e
Babel 6
We were finally able to upgrade to Babel 6.
We strongly recommend using npm@3 as Babel 6 is very modular and the npm@3 default deduplication is important for performance and size reasons.
This change has no effect on what Babel version you use in your own project. We bundle our own Babel version.
TAP support
You can now get TAP output instead of our builtin reporter by using the
--tapflag.Use any of the myriad of TAP reporters. Like the tap-nyan reporter as seen above.
This is how we'll support custom reporters in AVA. Write a TAP reporter. We're not interested in creating another silo of test runner specific reporters.
New default reporter
We built a new minimal reporter that's now the default. You can get back the old verbose reporter with the
--verboseflag.Other
- Breaking
Deeply recurse directories. Previously AVA only looked for test files in the immediate subdirectory. Now it will look in subdirectories at any level. 72e87d9
Ignore files in directories named
fixturesandhelpers. f6cef7fCache Babel transpiled code. This will improve startup performance considerably. 0daec3e
Make
--requirerelative to where the command is run. ae446f0Show full stack trace for non-assert errors. cbea003
Fix promise assertions. e52db69
French translation of the docs. Thanks to @forresst :) 8346d35
Changes
🎄 Happy holidays from James, Vadim, and Sindre! 🎉
- 0.8.x
0.8.0
14 Dec 2015Don't use the user local Babel when available. Instead always use the the built-in Babel. This will let you use Babel 6 in your project even though we don't yet support Babel 6. d0c370a
Add ability to skip individual assertions with
t.skip(). 357622cNode.js-style
--requireCLI argument. 6081389
Highlights
Don't use the user local Babel when available. Instead always use the the built-in Babel. This will let you use Babel 6 in your project even though we don't yet support Babel 6. d0c370a
Add ability to skip individual assertions with
t.skip(). 357622cNode.js-style
--requireCLI argument. 6081389Forward all test file output to
stderron the main process. 3f2e67aAllow deep equality comparison of values with circular references in assertions. 56cd652
Allow destructuring of the
tparameter. e0f31e8Use
empower-corefor better assertion tracking and performance. 072ab85Stop hiding source of syntax errors. ad7ae19
Add filename to failed test title. 8a67704
Add default message to the output of
t.fail(). da3c7a8
Changes
- 0.7.x
0.7.0
30 Nov 2015Use the local AVA version if available when running
$ avafrom the CLI. 2f7ac92Guard against time manipulation by mocking modules like Sinon. b88c2ba
!(cloud.githubusercontent.com/assets/170270/11463…)
Breaking changes
There are some breaking changes in this release that significantly improves the test interface.
test()is now only for synchronous or promise/observable returning testsThe main
test()interface is now synchronous by default and can be made asynchronous by returning a promise/observable or using a async/generator function (which implicitly returns a promise).You no longer have to call
t.end()in synchronous tests:test(t => { t.pass(); - t.end(); })You can no longer use
test()for callback-style APIs, so we've introduced a new "callback mode"test.cb().-test(t => { +test.cb(t => { fn(err => { t.ifError(err); t.end(); }); });t.plan()will no longer auto-end testsYou will now have to explicitly end tests with callback-style APIs. Previously,
t.plan()doubled as both an assert counter and ending the test when the assertion count was reached. This was a mistake. It's now only an assert counter. We are now able to warn on too many async assertion which were previously not possible. Note thatt.end()only works in "callback mode"test.cb().-test(t => { +test.cb(t => { t.plan(1); fn(err => { t.ifError(err); + t.end(); }); });More info here: github.com/sindresorhus/ava
Highlights
Test methods are now chainable. You can for example do
test.serial.skip(). d874ec9Use the local AVA version if available when running
$ avafrom the CLI. 2f7ac92Guard against time manipulation by mocking modules like Sinon. b88c2ba
Improve the behavior of the
--serialflag. 7ad7501
Changes
- 0.6.x
0.6.1
24 Nov 2015Removes git dependency for more reliable installs. 588ab18
A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.