Http-proxy-middleware version 2.0.1 offers subtle but beneficial updates compared to its predecessor, version 2.0.0. Both versions serve as valuable tools for developers seeking to streamline proxy setups within Node.js environments, specifically for Connect, Express, and BrowserSync applications. The core functionality remains consistent: simplifying the creation of proxy middleware with a concise, one-liner approach.
Examining the dependency changes reveals a focus on keeping pace with the evolving JavaScript ecosystem. Version 2.0.1 features updated development dependencies, reflecting advancements in testing, linting, and overall code quality tools. Notable updates include newer versions of jest, eslint, typescript and related type definitions. These updates likely bring improved performance, enhanced type safety, and better compatibility with modern JavaScript standards.
While the core dependencies remain the same, the updated development dependencies signal ongoing efforts to maintain a robust and well-tested library. Developers upgrading should benefit from these improvements indirectly through a more reliable and maintainable codebase. The changes in development dependencies suggest that version 2.0.1 has better support for the latest JavaScript and TypeScript features and practices. The release date informs developers about the recency of the updates, with version 2.0.1 released later, ensuring it includes the latest patches and optimizations. While the unpacked size is slightly smaller in 2.0.1 potentially indicating some optimisations.
All the vulnerabilities related to the version 2.0.1 of the package
Denial of service in http-proxy-middleware
Versions of the package http-proxy-middleware before 2.0.7, from 3.0.0 and before 3.0.3 are vulnerable to Denial of Service (DoS) due to an UnhandledPromiseRejection error thrown by micromatch. An attacker could kill the Node.js process and crash the server by making requests to certain paths.
http-proxy-middleware can call writeBody twice because "else if" is not used
In http-proxy-middleware before 2.0.8 and 3.x before 3.0.4, writeBody can be called twice because "else if" is not used.
http-proxy-middleware allows fixRequestBody to proceed even if bodyParser has failed
In http-proxy-middleware before 2.0.9 and 3.x before 3.0.5, fixRequestBody proceeds even if bodyParser has failed.
