Version Details and Security Vulnerabilities

📦

ts-jest

29.1.2

Comparision Betweeen 29.1.2 and 29.1.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

300.67 KB

300.28 KB

Version 29.1.2 Details

Ts-jest has released a new version, 29.1.2, following the previous stable version 29.1.1. Both versions serve as Jest transformers, enabling developers to test TypeScript projects seamlessly with source map support. Core functionality remains consistent, ensuring a smooth testing experience. Examining the differences reveals subtle yet potentially impactful updates. The node-fetch dependency has been updated from version 3.3.1 to 3.3.2. Also, the json-schema-to-typescript dependency was updated from version ^13.0.1 to ^13.0.2. While the dependencies remain mostly consistent, the unpacked size of the package increased slightly from 307,489 bytes to 307,888 bytes.

These updates suggest improvements behind the scenes, possibly bug fixes, performance enhancements, or minor feature additions. Developers should update primarily because of the bug fixes/security updates that the updated packages include, and also to keep their project dependencies aligned with the packages's dependencies, as failing to update carries risk of breaking changes in the future. Ts-jest continues to rely on a robust ecosystem of tools, including Jest, TypeScript, Babel, and various linting and utility libraries. Developers leveraging ts-jest can expect continued compatibility with these tools, facilitating efficient and reliable TypeScript testing workflows. Before upgrading, review the changelog and test suite results to ensure compatibility with your specific project setup.

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.