NodeJS Buffer interface has a maximum length of 2147483647 bytes, but what if we need more ?
One solution is to distribute the data on multiple buffers and map each index to one of the buffers. This is what the library is about, no need to do the mapping, you'll get the same interface as the original 'Buffer' but with infinite Buffer size which is around (2147483647 * 2^32 -1) = 9 x 10^9 gb).
not all Buffer methods are supported.
npm install fatbuffer --save
FatBuffer.alloc(length)
.isBuffer(obj)
returns true if obj was a Buffer or an instance of FatBuffer.
.isFatBuffer(obj)
returns true if obj was an instance of FatBuffer.
length: length in bytes.
Returns length in bits.
const FatBuffer = require("fatbuffer")
const buffer = FatBuffer.alloc(2147483647*5);
buffer[2147483647*3]=255;
console.log(buffer[2147483647*3]) // 255
Array of buffers and some mapping techniques.
FAQs
a Buffer but a fat one.
The npm package fatbuffer receives a total of 0 weekly downloads. As such, fatbuffer popularity was classified as not popular.
We found that fatbuffer demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
/Research
Malicious npm package impersonates Nodemailer and drains wallets by hijacking crypto transactions across multiple blockchains.
Security News
This episode explores the hard problem of reachability analysis, from static analysis limits to handling dynamic languages and massive dependency trees.
Security News
/Research
Malicious Nx npm versions stole secrets and wallet info using AI CLI tools; Socket’s AI scanner detected the supply chain attack and flagged the malware.