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

token-boy

v0.0.4

Published

Serves a token of given bit length with given encoding, digested by default.

Downloads

9

Readme

Build Status

token-boy

Serves a token of given bit length with given encoding, digested by default.

Collision detection logic is left out as it should be specific to your application.

##Install

For node

npm install token-boy --save

For browsers

bower install token-boy

or

git clone [email protected]:zeusdeux/token-boy.git

If you plan to use it with browserify, then just require index.js.
If you plan to use it directly in the browser, then include browser/token-boy.min.js. This will export a global require function.
You can then do:

<script>
  var tokenBoy = require('token-boy')();
  var token = tokenBoy().token; //returns a 128 bit, base64 encoded, digested token
</script>

##Usage

###Simple usage

var tokenBoy = require('token-boy')()
var token = tokenBoy().token //returns a 128 bit, base64 encoded, digested token

###Advanced usage

var tokenBoy = require('token-boy')('hex') //specifying default encoding to be hex
var token

token = tokenBoy().token //returns a 128 bit, hex encoded, digested token
token = tokenBoy(256,'base64').token //returns a 256 bit, base64 encoded, digested token
token = tokenBoy(128,'base64', false).token //returns a 128 bit, base64 encoded, non-digested token
token = tokenBoy(512, 'ascii', false).token //returns a 512 bit, ascii encoded, non-digested token

//note:
//both of these return a 512 bit, default encoding ('hex' in this case) encoded, digested token
//this is because ascii is not a valid digest encoding type as of node v0.10.29
token = tokenBoy(512, 'ascii', true).token
token = tokenBoy(512, 'ascii').token

As of Node v0.10.29
Encodings supported are:

  • ascii
  • utf8
  • utf16le
  • ucs2
  • base64
  • binary
  • hex

Default encodings supported are:

  • binary
  • base64
  • hex

The default encodings supported are only a subset of encodings as the digest() method documentation asks us to only use these. If it is needed, I shall add support for all encodings to be used as default encodings but I don't see the need for it right now.

##Changelog

  • 0.0.4
    • bugfixes and documentation fixes
    • fixed the broken 0.0.3 version
  • 0.0.3 (do not use this version)
    • bugfixes