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

js-google-auth

v2.0.1

Published

This wrapper provides you simplified functionality to handle the Google OAuth2 process. The token is stored in the local storage and will be restored after page reload until you sign-out the user.

Downloads

5

Readme

JavaScript Google OAuth2 Wrapper

This wrapper provides you simplified functionality to handle the Google OAuth2 process. The token is stored in the local storage and will be restored after page reload until you sign-out the user.

This module is considered to work in the browser and in Electron applications.

More information about the background process: https://developers.google.com/identity/protocols/OAuth2UserAgent

You can use the token to proceed with other wrappers:

You can use the token as well for any other Google REST API.

Installation

npm install --save js-google-auth

Usage

// Load module
import GoogleAuth from 'js-google-auth';

// Create new instance
const auth = new GoogleAuth({
  clientId: 'your-google-client-id',
  clientSecret: 'your-google-client-secret',
  redirectUri: 'your-script-uri',
  scope: 'https://www.googleapis.com/auth/contacts'
});

// Use methods
if (!auth.getToken()) {
  auth.signIn();
} else {
  console.log(`Token: ${auth.getToken()}`);
}

Methods

constructor(options)

While creating a new instance, the constructor method is called.

Options:

  • clientId - string to receive from the Google API console
  • clientSecret - string to receive from the Google API console
  • redirectUri - string to configure in the Google API console (not required for Electron)
  • scope - string/array one as string or more as array, see overview at Google (optional)
  • onTokenChange - function which is called on every token change (optional)

Example:

const auth = new GoogleAuth({
  clientId: 'your-google-client-id',
  clientSecret: 'your-google-client-secret',
  redirectUri: 'your-script-uri',
  scope: [
    'https://www.googleapis.com/auth/contacts',
    'https://www.googleapis.com/auth/drive'
  ],
  onTokenChange: (token) => {
    // Use this function to update the token
    // for your custom API scripts.
    // For our wrappers it is done automatically.
  }
});

getToken()

Returns token or null. Use this function to check if the user is signed-in or not.

signIn(callback)

Starts the sign-in process. In the browser with redirect, in Electron within a new browser window.

After successful sign-in, the credentials are stored in the local storage and restored after reload.

The callback function is optional.

Example:

auth.signIn((error) => {
  if (error) console.error(error);
  else console.log('signed-in');
})

signOut(callback)

Removes the credentials from the instance and from the local storage.