npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

bufsp

v1.0.3

Published

Buffer Frame Serialization Protocol (BUFSP), parse pipelining chunks.

Readme

BUFSP

Buffer Frame Serialization Protocol (BUFSP), parse pipelining chunks.

NPM version Build Status

BUFSP is a low level protocol designed specifically for socket commutation with buffer frames.

As we know, chunks output from net socket mostly are not represent integrated messages. Sometimes a chunk include onemore integrated messages, or a number of chunks represent a integrated message. How can we get message one by one from these chunks? BUFSP is designed.

It is a subset of Redis RESP.

There are only two type:

  • Errors, the first byte of the reply is "-"
  • Bulk Strings, the first byte of the reply is "$"

BUFSP Errors

BUFSP error is use to response a error from one side to another. The basic format is:

"-Error message\r\n"

Become to buffer:

<Buffer 2d 45 72 72 6f 72 20 6d 65 73 73 61 67 65 0d 0a>

It will be decoded to new Error(message).

BUFSP Bulk Strings

Bulk string is used in order to represent single binary safe string, binary buffer, or null.

Bulk Strings are encoded in the following way:

  • A "$" byte followed by the number of bytes composing the string (a prefixed length), terminated by CRLF.
  • The actual string or binary data.
  • A final CRLF.

So the string "foobar" is encoded as follows:

"$6\r\nfoobar\r\n"

the string "中文" is encoded as follows:

"$6\r\n中文\r\n"

the binary buffer new Buffer(10).fill(0) is encoded as follows:

"$10\r\n\0\0\0\0\0\0\0\0\0\0\r\n"

When an empty string is just:

"$0\r\n\r\n"

RESP Bulk Strings can also be used in order to signal non-existence of a value using a special format that is used to represent a null value. In this special format the length is -1, and there is no data, so a null is represented as:

"$-1\r\n"

This is called a Null Bulk String. It can be use as heartbeat packet.

Install

Install with npm

npm install bufsp

Usage

API

var Bufsp = require('bufsp');

Class Bufsp

new Bufsp([options])

Bufsp is a EventEmitter similar to Writable stream. It accept BUFSP chunks, parse them, produce integrated buffer frames | strings | null | error. Readable stream can be piped to bufsp.

  • options {Object}
    • encoding {String} use to encode or decode between buffer and string, default to 'utf8'
    • returnString {Boolean} produce string with encoding option, default to false
var socket = net.connect(options);
var bufsp = new Bufsp({returnString: true});

bufsp.on('data', function(message) {
  // received data and decode to message
  console.log(JSON.stringify(message))
});

socket.pipe(bufsp);
// or
// socket.on('data', function (chunk) {
//   bufsp.write(chunk);
// });


// server side send a message in BUFSP buffer to the client
server_socket.write(bufsp.encode(JSON.stringify({_id: 'xxx', name: 'test'})));

Class Method: Bufsp.encode(value[, encoding])

Encode value to BUFSP buffer.

  • value {Buffer|String|null|Error} data to encode
  • encoding {String} String Encoding of String chunks, accept all Buffer encodings, default to undefined

Return buffer.

var nullBuf = Bufsp.encode(null);
// <Buffer 24 2d 31 0d 0a>

var errorBuf = Bufsp.encode(new Error('error!'));
// <Buffer 2d 45 72 72 6f 72 20 65 72 72 6f 72 21 0d 0a>

var msgBuf = Bufsp.encode(JSON.stringify({_id: 0, name: 'bufsp'}));
// <Buffer 24 32 34 0d 0a 7b 22 5f 69 64 22 3a 30 2c 22 6e 61 6d 65 22 3a 22 62 75 66 73 70 22 7d 0d 0a>

var binBuf = Bufsp.encode(new Buffer([0xff, 0xff, 0xff]));
// <Buffer 24 33 0d 0a ff ff ff 0d 0a>

Class Method: Bufsp.decode(buffer[, encoding])

Decode BUFSP buffer to integrated buffer frame or string.

  • buffer {Buffer|String|null|Error} data to decode
  • encoding {String} String Encoding of String chunks, accept all Buffer encodings, default to undefined

Return {Buffer|null|Error} data, if encoding is provided, it will try to return string. if buffer can't be decode, it will throw error.

Bufsp.decode(Bufsp.encode(null));
// null

Bufsp.encode(Bufsp.encode(new Error('error!')));
// { [Error: error!] }

bufsp.write(chunk)

Feed BUFSP chunk and parse it. bufsp will emit data event while a integrated data decoded.

bufsp.end([chunk])

Call this method when no more chunk will be written to bufsp, then finish event emit.

bufsp.encode(value[, encoding])

The same as Bufsp.encode. It will use constructor's options.encoding if omitted.

bufsp.decode(buffer[, encoding])

The same as Bufsp.decode. It will use constructor's options.returnString && options.encoding if omitted.

Event: 'error'

  • error {Error}

Emitted when an error occurs.

Event: 'data'

  • data {Buffer|String|null|Error}

Emitted when integrated buffer frame | string | null | error produced. Notice that the data may be null or Error object, it is not general stream chunk.

Event: 'drain'

Emitted when chunk have been parsed or need more chunks for parsing.

Event: 'finish'

The finish event is fired after .end() is called and all chunks have been processed.

License

MIT © teambition