Version Details and Security Vulnerabilities

📦

ts-jest

29.2.0

Comparision Betweeen 29.2.0 and 29.1.5

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

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

Unpacked Size

318.62 KB

300.8 KB

Version 29.2.0 Details

Ts-jest versions 29.2.0 and 29.1.5 both serve as Jest transformers, enabling TypeScript project testing with source map support. While the core functionality remains consistent, several dependency updates and modifications are present, potentially impacting developer workflows.

A notable change is the update of several development dependencies in v29.2.0. @typescript-eslint/parser and @typescript-eslint/eslint-plugin are bumped to version ^7.15.0 from ^7.13.0. Typescript is updated to version ~5.5.3 from ~5.1.3 and Prettier is downgraded to version ^2.8.8 from ^3.3.2. Also, new in v29.2.0, there is the addition of the package @types/node with version 20.14.10. @commitlint/cli and @commitlint/config-angular are downgraded to 18.6.1 from ^19.3.0. These updates might introduce breaking changes or new features, which may necessitate adjustments in project configurations or code.

For developers, it's crucial to evaluate the impact of these dependency updates. Thorough testing is recommended after upgrading to v29.2.0 to ensure compatibility and stability. The TypeScript update in v29.2.0 could bring improved type checking and language features, but might require code adjustments if breaking changes are introduced.

The releaseDate also stands out, showing that v29.2.0 was released on 2024-07-08, a few weeks after version 29.1.5, released on 2024-06-16. This indicates a relatively active development cycle. Developers should always consult the changelog and release notes for detailed information on specific changes, bug fixes, and potential migration steps when upgrading between versions. The core features for testing TypeScript with Jest remain the same, with the focus on dependency updates and continuous improvements.

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.