Node-fetch is a lightweight module that ports the window.fetch API, familiar to browser-based JavaScript developers, to Node.js and io.js environments. Versions 1.7.1 and 1.7.2 share the same core functionality, providing a promise-based interface for making HTTP requests. Both rely on the 'encoding' and 'is-stream' modules as dependencies for handling character encodings and stream processing, respectively. Crucially, the developer dependencies are identical, including tools like Bluebird for promise management, Chai and Chai-as-promised for testing, Codecov for code coverage reporting, Form-data for handling multipart form data, Istanbul for code coverage analysis, Mocha for test running, Parted for stream parsing, Promise for promise polyfills, and Resumer for resumable streams. This means the underlying testing and development environment remained consistent between releases.
The key difference lies in the release dates and potential bug fixes or minor improvements introduced in version 1.7.2. Released on August 8, 2017, version 1.7.2 followed version 1.7.1, which was released on June 3, 2017. While the provided data doesn't explicitly detail the changes, the short timeframe suggests that version 1.7.2 likely addresses bug fixes, performance tweaks, or minor enhancements discovered since the previous release. Developers should therefore prefer Node-fetch version 1.7.2 over 1.7.1 to benefit from these improvements, ensuring greater stability and potentially better performance in their Node.js applications. Always consult the changelog or release notes (if available) for a comprehensive understanding of the specific changes between versions.
All the vulnerabilities related to the version 1.7.2 of the package
node-fetch forwards secure headers to untrusted sites
node-fetch forwards secure headers such as authorization
, www-authenticate
, cookie
, & cookie2
when redirecting to a untrusted site.