Version Details and Security Vulnerabilities

📦

typescript-transform-paths

3.4.0

Comparision Betweeen 3.4.0 and 3.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

90.05 KB

76.39 KB

Version 3.4.0 Details

Typescript-transform-paths version 3.4.0 introduces several notable updates compared to version 3.3.1, primarily focusing on enhanced support for newer TypeScript versions and improved developer tooling. The headline is the support for newer Typescript versions.

A key upgrade is the updated peer dependency, now explicitly compatible with TypeScript versions >=3.6.5. The most recent version bumps the typescript devDependency from version 4.3.5 to 4.8.4 and introduces @types/ts-expose-internals npm aliased dependency on ts-expose-internals@4.8.4. This enhancement ensures smoother integration and avoids potential compatibility issues with projects utilizing recent TypeScript features and syntax while leveraging internal APIs.

Furthermore, the development dependencies have been significantly updated. Jest has been updated from 27.0.6 to 29.2.1, ts-jest from 27.0.4 to 29.0.3, ts-node from 10.1.0 to 10.9.1, prettier from 2.3.2 to 2.7.1, @types/jest from 26.0.24 to 29.2.0, @types/node from 16.4.10 to 18.11.2, and @types/minimatch from 3.0.5 to 5.1.2. The standard-version has been bumped up to version 9.5.0 from 9.3.1. These updates reflect improvements in testing, code formatting, and overall development workflow, benefitting developers contributing to or extending the library.

While the core functionality of transforming module resolution paths based on TypeScript path mappings remains the same, developers upgrading to version 3.4.0 can expect a more robust and well-supported experience, especially when working with the latest TypeScript versions and modern JavaScript tooling. The increased file count and unpacked size hints some enhancements to the codebase and potentially more comprehensive functionalities.

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.