Buffer Allocation Patterns | NodeBook

[giscus[bot]]

Buffer Allocation Patterns | NodeBook

Learn and Master the complex parts of the Node.js Runtime. From V8's Turbofan optimizer to production deployments. Each chapter includes hands-on labs, real-world examples, and performance insights. The definitive guide to becoming a Node.js expert.

https://www.thenodebook.com/buffers/allocation-patterns

[VesperQuartz]

Am confused by this fix

 
// 1. Allocate a new, clean buffer that you control.
const headerBuffer = Buffer.alloc(16);
// 2. Create a temporary view to copy from the source.
const sourceView = Buffer.from(arrayBuffer, 0, 16);
// 3. Explicitly copy the data into your own buffer.
sourceView.copy(headerBuffer);```

Where did 16 come from and how did you know to use 16?
 

[ishtms]

Hi @VesperQuartz, 16 is just an example number I picked for this. It was a follow up for this part of the chapter. In short, we wanted to extract the header of any file and assumed that the header takes the first 16 bytes.

For your usecase, you'd choose the size based on what you actually need to read. If you're checking file headers, some formats need just 4 bytes to identify, others might need 64 or more, so you'd allocate exactly as much space as your specific use case requires.