Version Details and Security Vulnerabilities

📦

typescript-transform-paths

1.1.3

Comparision Betweeen 1.1.3 and 1.1.2

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

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

Unpacked Size

14.87 KB

10.93 KB

Version 1.1.3 Details

Typescript-transform-paths, a utility for transforming absolute imports to relative paths in Typescript projects, saw a release of version 1.1.3 following closely on the heels of version 1.1.2. While both versions share the core functionality and MIT license, several key differences cater to developers focused on dependency management, code health, and build processes.

The most notable change lies in the slash dependency. Version 1.1.3 upgrades this dependency to ^3.0.0 from ^2.0.0 in version 1.1.2. This update likely addresses bug fixes, performance improvements, or new features within the slash package itself, affecting how paths are normalized within the transform. Developers should consult the slash package changelog to understand the specific implications of this upgrade.

Furthermore, the @types/node dev dependency sees an update from ^10.12.21 to ^12.0.2. This indicates a shift towards compatibility with newer Node.js versions, potentially opening doors to utilizing more recent Node.js features within the development or build pipeline related to Typescript transformations. The @types/slash dev dependency has also been removed, probably because the typings are now directly included in the slash package. The standard-version dependency also changes from version 4.4.0 to 6.0.1, providing fixes and improvements in the release process.

Additionally, the distributed size of the package increased from 11190 bytes to 15230 bytes, probably due to the updated dependencies. Developers should consider these changes when deciding which version to adopt, particularly if their projects have strict dependency constraints or rely heavily on specific Node.js versions.

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.