http-deceiver-fixes is a maintenance fork of the http-deceiver module, which provides a low-level interface to Node.js's internal HTTP parser. Its primary function is to enable "deception" or advanced manipulation of raw HTTP streams and parsed messages, often used in sophisticated networking scenarios like implementing alternative HTTP protocols (e.g., SPDY, HTTP2) or handling specific parser edge cases. The original http-deceiver (last published in 2016, v1.2.7) has been largely unmaintained, leading to DeprecationWarning's and potential runtime errors in modern Node.js environments due to its reliance on process.binding('http_parser'). This http-deceiver-fixes package, currently at v1.2.8, aims to integrate critical bug fixes (e.g., for handling multiple body chunks) that were unmerged in the original project, providing continued compatibility for systems dependent on this functionality. Its release cadence is irregular, driven by necessary patches, and it serves as a stop-gap solution for projects facing issues with the abandoned upstream.
npm install http-deceiver-fixesVerified import paths — ran on the pinned version, not inferred.
This quickstart demonstrates how to initialize `http-deceiver-fixes` by wrapping an internal HTTP parser (obtained from `http.IncomingMessage`) and then feeding raw HTTP data to it, showing its low-level parsing interception capabilities.
There is no direct fix within user code. This typically requires the library itself to be updated to use publicly available APIs or a robust fallback to `http-parser-js` for compatibility. For critical applications, consider migrating to alternative, actively maintained HTTP parsing or proxying solutions that do not rely on deprecated Node.js internals.
Review the `test/` directory within the package's source code for examples of how the `Deceiver` class is instantiated and used with Node.js `http` and `net` modules. Understand the underlying `http_parser` concepts for effective manipulation.
Before adopting, assess the long-term maintenance needs of your project. Be prepared to contribute patches or consider alternative solutions if active development or support for new Node.js versions becomes critical.
This is a warning and might not immediately stop execution. While there's no direct userland fix, the long-term solution involves ensuring the library (or a replacement) correctly falls back to `http-parser-js` or uses modern Node.js `http` module APIs. Consider pinning to an older Node.js version if this warning is critical, or migrating away from this library.
This indicates a hard incompatibility with your current Node.js version. You must either downgrade your Node.js runtime to a version compatible with the library's internal API usage (typically Node.js < 12) or replace `http-deceiver-fixes` with a different library that provides similar functionality without relying on deprecated Node.js internals.
No dependency data recorded yet.