node-client-sessions VS a12n-server

If all you are interested in is logging in with a password, then rolling your own auth middleware and adding something like encrypted client sessions (see https://github.com/mozilla/node-client-sessions) will get you pretty far. If you need to support logging in with Facebook or Google or LDAP or Apple, or all of the above, then Passport is your friend (even if they’re a confusing friend).

const x = 'const';const x = 'not-const';// Will give an error: 'constant 'x' has already been defined' I realise that it is not yet standardized across all browsers - but I'm only interested in the context of Node.js V8, and I've noticed that certain developers / projects seem to favor it heavily when the var keyword could be used to the same effect.

I wrote a small OAuth2 serer with NodeJS: https://github.com/curveball/a12n-server

a12n-server. Lightweight, Node.js. Just run npm start to run it and all based around OAuth2. I've been working on this for almost 5 years =)

There's open source OAuth2 providers too that you can self-host. a12n-server is one of them, and the steps to get it up and running are:

Another OAuth2 server, that's well on the other side of the heavyweight spectrum vs. keycloak:

https://github.com/curveball/a12n-server

I'm working on one that supports posgresql (and also mysql, sqlite): https://github.com/curveball/a12n-server