Bump ava from 0.25.0 to 3.15.0

[dependabot-preview]

Bumps ava from 0.25.0 to 3.15.0.

Release notes

Sourced from ava's releases.

3.15.0

Automatic snapshot file removal

When you stop using snapshots in a test file, the next time you run ava --update-snapshots we'll remove the left-over snapshot files. Thanks @ninevra! 4f093ab

TAP improvements

@tymfear has been on a roll improving our TAP reporter. t.log() output is now compliant with the spec 99ab93a. Tests that did not run due to timeouts are now reported 98595dae58209a9062d0238c7a3dd7078a9962d1.

Next-generation configuration

AVA 4 will add full support for ESM configuration files as well as allowing you to have asynchronous factory functions a2f2614cc1e34fb9a7aa204b37b3b25559f203d9. If you're using Node.js 12 or later you can opt-in to these features in AVA 3 by enabling the nextGenConfig experiment. Say in an ava.config.mjs file:

export default {
	nonSemVerExperiments: {
		nextGenConfig: true
	},
	files: ['unit-tests/**/*]
};

This also allows you to pass an .mjs file using the --config argument.

With this experiment enabled, AVA will no longer have special treatment for ava.config.js files. Instead AVA follows Node.js' behavior, so if you've set "type": "module" you must use ESM, and otherwise you must use CommonJS.

You mustn't have an ava.config.mjs file next to an ava.config.js or ava.config.cjs file.

---

See avajs/ava@v3.14.0...v3.15.0 for all changes.

3.14.0

Snapshot ordering

With this release, snapshot files are now ordered based on test declaration, not completion. This makes it easier to compare the human-readable reports to your test file, and also stops the .snap from changing when the reports themselves don't. You'll want to rebuild snapshots after upgrading to this release to isolate any changes. Thanks @ninevra! e66b54ce61d8bb16bbcd15b7fb90893d02e5a65c

Shared workers

We’ve been working on making AVA more extensible. One major step on this path is our new shared worker support: run code in the main process, communicate with test workers and influence execution. Find out more in our shared workers recipe.

---

See avajs/ava@v3.13.0...v3.14.0 for all changes.

3.13.0

• t.passed can now be used in tests and teardown functions. Thanks @tymfear! 900dc6d46a1f8728dddfab1e42caef1fa8a51c85
• In AVA 4, you'll no longer be able to pass null as the expectation for t.throws() & t.throwsAsync(). You can opt in to this early by enabling the disableNullExpectations experiment. Thanks @JSimoni42! f328a6933af7aca221b08f694bb14b03701eca68
• The Enzyme recipe has been updated. Thanks @jonathansamines! db5d2c369178b78dfbd899d002a141a05655ccdc
• The TypeScript recipe has been updated. Thanks @SephReed! a3379fad3893468309a43b4b56d290f94933f082

Commits

• 32c5425 3.15.0
• 0f69088 Update dependencies
• a2f2614 Next-generation configuration loading
• 711bcf2 Housekeeping
• 4f093ab Remove snapshot files when a test file stops using snapshots
• 98595da Fix timeout reporting in TAP reporter
• 3fe4c40 Only create the cache directory when needed (#2628)
• 99ab93a Upgrade supertap and print t.log entries according to TAP diagnostics spec
• 5d3b200 3.14.0
• 9b2bd5f Update dependencies
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

If all status checks pass Dependabot will automatically merge this pull request.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Automerge options (never/patch/minor, and dev/runtime dependencies)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)

[dependabot-preview]

One of your CI runs failed on this pull request, so Dependabot won't merge it.

• continuous-integration/travis-ci/push

Dependabot will still automatically merge this pull request if you amend it and your tests pass.