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 🙏

© 2025 – Pkg Stats / Ryan Hefner

jschmold-sessions

v0.0.1

Published

A mini library intended to simplify how user sessions are managed

Downloads

5

Readme

node-sessions -- @jschmold/sessions

Aim

To create a user-session minilib that handles user sessions

How does it work?

Guessing one long string can be pretty hard, but what if an attacker gets it right? They'd only have to generate a single string and they'd be in. Even worse, what happens if a single-key session string is compromised?

This library handles sessions by requiring an end-user to know two things. They must know their persistent session id, and they must know their transient id. The persistent session id is how you'd go about recognizing a specific device, or a session in general. The transient is how you know that the user is actually the one doing the requests. Every time the user makes a request, you should call the next function on the session, save the new token, and inform the user what their new session token is. The session token string contains multiple pieces of data, adding to the overall authentication. If one piece of data is lost, it's not a valid session and the user must log in again.

How to use this library

If you are using strings across everything, this mini-lib is plug and play.

let myUserSession = new Session('the_users_id');

If you are looking to save a session, do something like this

sessionId = myUserSession.sessionToken;

If you are looking to validate a session

myUserSession.validate(inputUserId, inputSessionTokenString); // returns true or false
// if validated, do this
myUserSession.next();
// save new token in database
// return token to user

What about userIds of different kinds?

This one's pretty easy. This is assuming you're using ObjectID

function idCompare(item1: ObjectID, item2: ObjectID) {
  return item1.toHexString() === item2.toHexString();
}
Session.setIdComparator(idCompare);

What if I am paranoid and want to have longer transient/persistent ids for my token?

This one is also pretty easy.

To set the transient id generator DToken.setTransientGenerator(yourStringGenerator), and to set the persistent: DToken.setPersistentGenerator(yourStringGenerator).

How do I generate documentation?

Run npm i -g typedoc, then npm run gendocs