Version Details and Security Vulnerabilities

📦

tsconfig-paths-webpack-plugin

2.0.0

Comparision Betweeen 2.0.0 and 1.4.0

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

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

N/A

Unpacked Size

N/A

Version 2.0.0 Details

The tsconfig-paths-webpack-plugin package, designed to seamlessly integrate TypeScript's path aliases with Webpack, saw a key update moving from version 1.4.0 to 2.0.0. While both versions share the core functionality of resolving modules according to the tsconfig.json paths, enabling cleaner and more maintainable code, the primary difference lies in the dependency tsconfig-paths. Version 2.0.0 upgrades this to ^3.1.1 from version ^2.7.2 in the older 1.4.0. This update likely brings improvements and bug fixes present in the newer tsconfig-paths version, potentially affecting how path resolution is handled.

Both versions include essential development dependencies like typescript, ts-node, webpack, and testing frameworks like tslint, ensuring a smooth development workflow for TypeScript projects using Webpack. Developers benefit from the MIT license, offering flexibility in usage and modification. The consistent inclusion of tools like husky and lint-staged underscores a commitment to code quality through pre-commit hooks for linting. If you are upgrading from 1.4.0 to 2.0.0, is a benefitial idea to review the tsconfig-paths changelog for potential breaking changes or new features in path resolution before upgrading to the new major version of tsconfig-paths-webpack-plugin, as they could impact your existing project's behavior.

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.