Version Details and Security Vulnerabilities

📦

ava

6.0.0

Comparision Betweeen 6.0.0 and 5.3.1

Identify the differences between the current version of the package and the previous one.

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

Unpacked Size

272.8 KB

265.25 KB

Version 6.0.0 Details

AVA version 6.0.0 brings several key updates and dependency changes compared to the previous stable version 5.3.1, making it a noteworthy upgrade for Node.js developers leveraging this test runner. A significant update can be seen in the dependencies. Version 6.0.0 updates acorn to 8.11.2 and chalk to 5.3.0, and introduces @vercel/nft as a new dependency for enhanced functionalities. Several other dependencies have been updated to newer major versions like cbor, p-map, and globby. These often include performance improvements, bug fixes, and potentially new features within those individual libraries. Developers should be mindful of potential breaking changes when upgrading, especially with major version bumps.

Breaking changes for developers are present in the devDependencies with c8 (coverage tool) up to 8.0.1 and xo (linter) to 0.56.0. expect testing library goes to 29.7.0.

In contrast, version 5.3.1 relied on older versions of key dependencies such as cbor, globby, ci-info as well as older devDependencies like c8 and xo. Dependency mem and p-event are dropped.

The new version contains a newer "@ava/typescript" devDependencies.

Developers should evaluate the updated dependencies and their individual changelogs to fully understand the implications of upgrading to AVA 6.0.0, ensuring a smooth transition and taking advantage of the latest features and improvements. The fileCount and unpackedSize are slightly higher in version 6.0.0, indicating a larger package size.

Security Vulnerabilities

This site is an independent open-source project and is not affiliated with, endorsed by, or sponsored by npm, Inc. or GitHub, Inc. The name “npm” is a registered trademark of npm, Inc., used here solely to describe compatibility and reference publicly available npm package data.