Version Details and Security Vulnerabilities

📦

jsdom

23.1.0

Comparision Betweeen 23.1.0 and 23.0.1

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

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

481

479

Unpacked Size

2.96 MB

2.82 MB

Version 23.1.0 Details

Jsdom version 23.1.0 introduces several noteworthy updates compared to the previous stable version, 23.0.1, making it an appealing upgrade for developers relying on this JavaScript implementation of web standards. A key change lies in the updated dependencies. The core "ws" (WebSocket) dependency has been bumped from version 8.14.2 to 8.16.0, potentially incorporating performance improvements and bug fixes related to WebSocket handling. The "cssstyle" dependency sees a significant jump from version 3.0.0 to 4.0.1, suggesting enhancements in CSS parsing and styling capabilities, which could impact how jsdom renders and interprets CSS.

On the development side, "eslint," a popular linting tool, has moved from version 8.54.0 to 8.56.0, likely bringing in new linting rules and code style checks to help maintain code quality during jsdom development. This change mostly affects contributors and maintainers of the jsdom package itself. Furthermore, the file count in the distributed tarball has increased slightly, from 479 to 481, and the unpacked size has also grown, from 2,959,120 bytes to 3,106,370 bytes. This indicates that new features, more extensive test cases, or expanded documentation could be delivered within the new version.

For developers using jsdom, the "cssstyle" upgrade stands out as potentially beneficial, as it could lead to more accurate CSS rendering and better alignment with browser behavior. While other dependency updates may not be immediately apparent, they contribute to the overall stability and improved performance of jsdom. The release date of January 5, 2024, signifies a recent update, making it worthwhile to explore the potential improvements for web development projects.

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.