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

check-token-from-serverless-env

v1.2.3

Published

check webtoken with userId and sent userId

Downloads

13

Readme

check token

This project serves serverless methods or where process.env exists.

After encrypting the userId inside the webtoken use this method to verify that the sent userId matches the userId inside the sent webtoken. This way it will not be necessary to query an external api to validate if the token matches the userId.

It also has a method to decrypt and encrypt the token based on the secretWebToken variable which must exist in env as its secret string.

Methods

encrypt

const {encrypt} = require('check-token-from-serverless-env')
try{
    let webtokenstring = encrypt({userId:"xpto", otherThing:234})
} catch(e){
    //
}

decrypt

const {decrypt} = require('check-token-from-serverless-env')
exports.handler = async (event) => {
    //get token from header or json body
    const webtokenstring = event?.headers?.token || eventBody?.token
    try{
        let myObject = decrypt(webtokenstring);
        //here supouse to have userId
        let userId = myObject?.userId
    } catch(e){
        //
    }
}

checkTokenByUserId


const {checkTokenByUserId} = require('check-token-from-serverless-env')


exports.handler = async (event) => {
    //get web token from header or json body
    const webtokenstring = event?.headers?.token || eventBody?.token
    //get userId from header or json body
    const userId = event?.headers?.userId || eventBody?.userId
    if(!checkTokenByUserId(webtokenstring, userId)){
        return {
            statusCode: 403,
            body: JSON.stringify({ success: false, message:["wrong token or userId"] })
        };
    }
    //...
}

| Remember: Use need to use your token like this

{
    userId: 'foo',
    ...
}

checkTokenByEvent


const {checkTokenByEvent} = require('check-token-from-serverless-env')


exports.handler = async (event) => {
    //get web token, userId or user_id from event (body, header, path)
    if(!checkTokenByEvent(event)){
        return {
            statusCode: 403,
            body: JSON.stringify({ success: false, message:["wrong token or userId"] })
        };
    }
    //...
}