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 🙏

© 2026 – Pkg Stats / Ryan Hefner

third-party-login

v1.0.12

Published

third party login integrate

Downloads

30

Readme

third-party-login

third party login plugin

npm install third-party-login --save

currently available for weibo weixin qq alipay

on todo list github douban taobao jd

usage:

const express = require('express');
const router = express.Router();
    
const config = require("./config");
const login = require("third-party-login");
    
// initialization
login.init(config);
    
// single platform
router.get("/login/weibo", login.weibo.auth);
router.get("/login/callback/weibo", login.weibo.token);
    
// multi-platforms
["weixin", "alipay", "qq"].forEach((key) => {
    router.get(`/login/${key}`, login[key].auth);
    router.get(`/login/callback/${key}`, login[key].token);
}

config:

{
    loadUserInfo: true,
    weibo: {
        redirect: "",
        app: {
            id: "",
            secret: ""
        },
        callbacks: {
            success: (data, req, res, next) => {

            },
            failure: (err, req, res, next) => {

            }
        }
    },
    weixin: {
        redirect: "",
        app: {
            id: "",
            secret: ""
        },
        scope: "snsapi_login",
        callbacks: {
            success: () => {

            },
            failure: () => {

            }
        }
    },
    alipay: {
        redirect: "",
        app: {
            id: ""
        },
        keys: {
            public: "",
            private: ""
        },
        scope: "auth_user",
        callbacks: {
            success: (req, res, next, data) => {

            },
            failure: (req, res, next, err) => {

            }
        }
    }
}

field explain for config

  • Common config

    loadUserInfo: if you want to load user info after you get token. set to true to load user info by token. Or false if uid is all you want.

  • platform config

    redirect: redirect url for platform after user login and authorized.

    app: your developer info of the platform. Get this on your developer's app page of the platform

    • id: app id
    • secret: app secret

    scope: authorize scope

    keys: public key and private key to sign and verify.(alipay only)

    • private: private key you generate by alipay's key tool.(for parameter sign)
    • public: alipay generated public key after you uploaded your public key.(for response verify)

    callbacks: callback function to handle response data

    • success: callback for success response data(token or user info)
    • failure: callback for failed response or error