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 🙏

© 2024 – Pkg Stats / Ryan Hefner

fast-varint

v1.0.1

Published

a faster varint

Downloads

242

Readme

fast varint

This is a fork of https://github.com/chrisdickinson/varint with a faster decoder (10x faster on int32)

encode whole numbers to an array of protobuf-style varint bytes and also decode them.

var varint = require('varint')

var bytes = varint.encode(300) // === [0xAC, 0x02]
varint.decode(bytes) // 300
varint.decode.bytes // 2 (the last decode() call required 2 bytes)

api

varint = require('varint')

varint.encode(num[, buffer=[], offset=0]) -> buffer

Encodes num into buffer starting at offset. returns buffer, with the encoded varint written into it. If buffer is not provided, it will default to a new array.

varint.encode.bytes will now be set to the number of bytes modified.

varint.decode(data[, offset=0]) -> number

decodes data, which can be either a buffer or array of integers, from position offset or default 0 and returns the decoded original integer.

Throws a RangeError when data does not represent a valid encoding.

varint.decode.bytes

if you also require the length (number of bytes) that were required to decode the integer you can access it via varint.decode.bytes. this is an integer property that will tell you the number of bytes that the last .decode() call had to use to decode.

varint.encode.bytes

similar to decode.bytes when encoding a number it can be useful to know how many bytes where written (especially if you pass an output array). you can access this via varint.encode.bytes which holds the number of bytes written in the last encode.

varint.encodingLength(num)

returns the number of bytes this number will be encoded as, up to a maximum of 8.

usage notes

If varint is passed a buffer that does not contain a valid end byte, then decode will throw RangeError, and decode.bytes will be set to 0. If you are reading from a streaming source, it's okay to pass an incomplete buffer into decode, detect this case, and then concatenate the next buffer.

License

MIT