* Upgrade XO
* Update TypeScript-related dependencies — Don't upgrade @sindresorhus/tsconfig to v6 since it requires TS 5.5 and we test with 5.2.
* Update dev dependencies
* Update dependencies
* Rebuild lockfile
* Upgrade CodeCov action
* Update reporter log instructions and remove deprecation warnings
* Make Node.js 22.6 the recommended development version
* Remove Node.js 21 from the engines list: It's no longer maintained by Node.js itself, see also <https://github.com/avajs/ava/blob/main/docs/support-statement.md>.
* Update dependencies
* Ignore snapshot fixture due to churn
* Remove errant log
* Update GHA actions
* Test type definition with TS 5.3
* Select latest LTS in Volta
* Remove unnecessary npx invocation
* Rebuild lockfile
* Work around legacy tap-based tests choking on our tsconfig.json
No idea why it's even resolving the config when there are no TypeScript tests to run.
* Update dependencies
* Rely on Node.js 18 language features
* Other small changes
* Upgrade to tap@18
* Develop and test with typescript@5.2
* Rebuild lockfile
---------
Co-authored-by: Mark Wubben <mark@novemberborn.net>
* Drop support for Node.js 16
* Change expected Node.js 18 to 18.18
* Change expected Node.js 20 to 20.8
* Add Node.js 21 to the test matrix
* Change snapshot tests to compare decompressed bitstreams
The snapshots are compressed differently in Node.js 21. The compression has been stable for many versions but that is not a guarantee, see https://github.com/nodejs/node/issues/50138 for background.
Change tests to compare the decompressed data instead.
* Test against typescript@5.0
* Default to Node.js 20
* Upgrade XO
* Add reporter logs for Node.js 20
* Update dev dependencies
* Reduce timeouts in reporter tests
This may cause CI failures especially on Windows, but we do waste a lot of time with these tests.
* Inline slash dependency
We need it available in CJS but the package is now ESM only. It's more bothersome to remember to not upgrade the dependency than to inline it.
* Update dependencies
* Rebuild lockfile
* Use latest Codecov action
* Upgrade XO and reformat
* Update dev dependencies
* Test with TypeScript 4.9
* Update dependencies
* Pin latest node@18 for Volta
* Use npm@9
* Rebuild lockfile
* Select Node.js version from Volta pin in most CI jobs
* Only pin npm when testing for lockfile churn; ensure npm@8 for Node.js 14
* Upgrade to TypeScript 4.8. Keep testing with 4.7 to ensure backwards compatibility.
* Update dev dependencies
* Update dependencies
* Tweak type definitions used in exports map for TS 4.8 compatibility. Duplicate and export shared types where appropriate, but don't export from the other export file since it seems to confuse things.
* Only test against TypeScript 4.7
* Move type definitions to entrypoints/
Only TS 4.7 will resolve them now, but it's cleaner.
* Use @sindresorhus/tsconfig
* Fix test TypeScript files, make compilable and lintable
* Use tsc directly, instead of tsd
* Add *.cts versions of type tests
* Reorganize type tests
* Use tsc directly, avoid npx, print actual version
Somehow `npx tsc` was pointing at an older version. Possibly the binstubs are corrupted in CI… somehow.
* Remove Node.js 17 support
* Add Node.js 18 support
* Use latest everything for CI tasks
* Configure Volta for managing development versions
* Update dependencies
* Update dev dependencies
* Update dependencies
* Remove concurrency limit for internal tests
* Test with TypeScript 4.6
* Update XO and fix formatting
* Fix reference to chalk's color level
* Upgrade XO and reformat
* Update dev dependencies
* Update production dependencies
* Rebuild lockfile
* CI: Continue when 'npm ls' errors in TypeScript compatibility job
This removes support for @ava/babel. Since enhanced assertions (power assert)
are provided through that package this also removes support for those. Same for
improper throws detection.
@ava/babel has seen no meaningful contributions since it was released at the
start of 2020. It's not clear how we'd make it work with ESM. It's clearer if we
can recommend tools like @babel/register and otherwise focus on plain Node.js &
TypeScript support.
* Test lockfile using npm 7.23
* Workflow updates
* Update codecov action
* Cache npm dependencies
* Simplify checkout
* Bump minimal Node.js versions
These should allow us to add features over AVA 4's lifetime using newly
available Node.js APIs.
* Update dev dependencies
* Update to TypeScript 4.4 and latest tsd
* Upgrade XO and reformat
* Update dependencies
* Rebuild lockfile
* Run XO with Node.js 16
It fails on older Node.js versions.
* Drop Node.js 15 support
* Require at least Node.js 12.22
* Test package-lock modifications with npm@7.11
* Upgrade to tap@15 for Node.js 16 compatibility
* Add Node.js 16 support
* Advertise GitHub Discussions
* Update issue template
* Remove badges from readme
* Avoid linting for every run in the test matrix. Lint with Node.js 10 only. This reduces check noise in GitHub PRs.
* Update GitHub Actions
* Remove Node.js 13 support
* Denote Node.js 12.17 as the future minimal Node.js 12 version
* Update dev dependencies
* Upgrade XO
* Update dependencies
* Rebuild lockfile
* Update dev dependencies
* Test with TypeScript 3.9
* Update dependencies
This includes a major update to Concordance, letting us print missing or extraneous objects in diffs with extra depth. See concordancejs/concordance#62.
* Rebuild package-lock
* Rename test directory to test-tap
This makes way for new, self-hosted tests inside a test directory
* Rewrite TypeScript test to use tsd; move into test-d directory
* Simplify npm run scripts
* Invoke nyc ourselves
* Don't store tap and nyc configuration in package.json
* Remove stdout / stderr from reporter test fixtures
These've ended up being flaky on Windows all of a sudden.
