This package, `buffer-builder`, provides a utility for incrementally constructing a Node.js `Buffer` without prior knowledge of its final size. It offers methods to append strings, existing buffers, and various integer/float types (e.g., `appendUInt32LE`, `appendFloatBE), as well as a byte fill operation. The current stable version is 0.2.0, last published over a decade ago in January 2015. Due to its age, it directly relies on the now-deprecated `new Buffer()` constructor, which poses significant security and usability issues in modern Node.js environments. This package is effectively abandoned, with no active development or updates to address compatibility with contemporary Node.js Buffer APIs (like `Buffer.from`, `Buffer.alloc`). Developers seeking similar functionality should consider actively maintained alternatives or Node.js's built-in `Buffer.concat` with an array of smaller buffers.
npm install buffer-builderVerified import paths — ran on the pinned version, not inferred.
Demonstrates initializing BufferBuilder, appending various data types, and retrieving the final Buffer, updated for modern Node.js Buffer API usage.
This package is effectively abandoned. For projects requiring Node.js v10+, consider alternative buffer building libraries or use native `Buffer.alloc()`, `Buffer.from()`, and `Buffer.concat()` with an array of buffers. If you must use this package with older Node.js versions, ensure your project's Node.js runtime is <10.0.0.
It is strongly recommended to migrate away from this package to actively maintained alternatives. If unable to migrate, thoroughly audit the package for security vulnerabilities and test rigorously with your specific Node.js version.
Always use `Buffer.from()` when creating a buffer from data (e.g., `Buffer.from([111, 114, 108, 100])`) or `Buffer.alloc()` for a zero-filled buffer of a specific size (e.g., `Buffer.alloc(10)`). The quickstart code reflects this change.
This package is incompatible with Node.js v10+. Either downgrade your Node.js version (not recommended) or replace `buffer-builder` with an actively maintained alternative that uses `Buffer.from()` or `Buffer.alloc()`.
This warning indicates the package uses an outdated and potentially insecure API. While it might still function, it's a strong signal to migrate to a modern, actively maintained buffer building library to avoid future breaking changes and security risks. You can suppress the warning with `--no-deprecation` but this is not recommended.
No dependency data recorded yet.