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

connect-session

v0.0.1

Published

Make connect session more convinient for REST API

Downloads

87

Readme

connect-session

It is a small project which help organize optional sessions in REST applications that uses connect/express. By default connect has only cookie session, that is not applicable and very unconvinient for API projects.

Usage

Generally it based on connect session.js code, so configuration and options almost the same.

For example you have a route that handle session management:

First i expect you will made some configuration and create middleware function:

//you config-session.js file
var connectSession = require('connect-session'),
    session = connectSession.session,
    header = connectSession.header;


var util = require('../lib/utils');

//you should replace this one with other store (but this used by default)
var MemoryStore = require('../lib/session/memory');

var loaders = [
    header({
        header: 'X-User-Session' //this used by default, so you can skip this
    })
];

var options = {
    store: new MemoryStore
}

module.exports.sessionCreate = session(loaders, options);

module.exports.sessionLoad = session(loaders, util.merge(options, {
    generateOnMissingSID: false
}));

var sessionCreate = require('./config-session').sessionCreate;

app.get('/sessions/new', sessionCreate, function(req, res) {
    res.json({ sid: req.sessionID});
})

This route will return newly created session and initialize session. You should understand that session will be available only in this route. What happen there:

First request will be processed by session middleware (by default it uses MemoryStore to store sessions) it will use header loader to try to find session id in default header 'X-User-Session' (to change this pass in header options { header: 'My-header'}). If session id will not be founded new session will be created and its sid will be returned.

Of course you expect that session will be loaded every time it can be loaded, to make this need to add in app general middleware:

var sessionLoad = require('./config-session').sessionLoad;

//do not forget add all needed middleware before!!!
app.use(sessionLoad);