Version Details and Security Vulnerabilities

📦

@testing-library/dom

8.3.0

Comparision Betweeen 8.3.0 and 8.2.0

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

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

Unpacked Size

2.81 MB

Version 8.3.0 Details

@testing-library/dom version 8.3.0 introduces subtle yet potentially impactful changes compared to version 8.2.0. Both versions share the same core dependencies, including packages like chalk, lz-string, aria-query, pretty-format, and Babel runtime and code-frame utilities, ensuring consistent handling of styling, string compression, accessibility considerations, and code transformation. Developer dependencies like jsdom, typescript, kcd-scripts, and testing-related utilities remain identical, indicating a stable development environment across both versions.

Key differences lie in the dist metadata. Version 8.3.0 exhibits a slightly larger unpacked size of 2949562 bytes compared to 8.2.0's 2943075 bytes, suggesting minor additions or modifications to the codebase that might involve new features and bug fixing. Furthermore, the releaseDate for 8.3.0 is September 7, 2021, while 8.2.0 was released on August 25, 2021, revealing a gap of approximately two weeks between releases and the newer version benefits of the latest patches and features.

For developers using @testing-library/dom, upgrading to 8.3.0 offers the potential upside of incorporating recent improvements and fixes. While the dependency footprint appears unchanged, the increased unpacked size signals internal updates that could enhance the library's functionality or robustness. Users should evaluate the changelog to identify specific changes relevant to their testing strategies.

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.