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 🙏

© 2023 – Pkg Stats / Ryan Hefner

express-google-oauth

v1.1.0

Published

Authenticate with google (via passport) and grant access to users who match an email whitelist

Downloads

13

Readme

express-google-oauth

Build Status

Usage

const app = require('express')()
const googleOauth = require('express-google-oauth')

googleOauth(app)

Options

The function can be called with a second options argument, with the following structure:

{
  google: {
    // oauth client ID
    clientID: string,

    // oauth client secret
    clientSecret: string,

    // callback, as configured in the google oauth console
    callbackURL: string
  },

  routes: {
    // route where the oauth flow is initiated
    init: string,

    // route where the oauth callback is handled
    callback: string

    // route where successful logins are redirected
    success: string,

    // route where failed logins are redirected
    failure: string
  },

  // comma-separated list of email addresses of people who are allowed to log in
  whitelist: string
}

To keep secrets out of your codebase, it is recommended to use the following ENV variables. If the the options.google section is undefined, values from process.env will be used by default:

  • GOOGLE_CLIENT_ID becomes opts.google.clientID
  • GOOGLE_CLIENT_SECRET becomes opts.google.clientSecret
  • GOOGLE_CALLBACK_URL becomes opts.google.callbackURL

The whitelist can also be stored in ENV, since it probably changes from one environment to the next:

  • GOOGLE_AUTH_WHITELIST becomes opts.whitelist

License

MIT