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

@wethecurious/wtc-auth-base-lib

v0.1.3

Published

Shared library for WTC exhibit dataServers using node backend that need permissions

Downloads

32

Readme

#@wethecurious/wtc-auth-base-lib

Shared library for WTC exhibit dataServers using node backend that need permissions

How to use it

##Auth

Auth is based in cognito groups, to change the group name that the user should belong to be authorized you can set COGNITO_USER_GROUP_NAME env var on .env.*.json files

{
  ...,
  "COGNITO_USER_GROUP_NAME": "MyAuthorizedGroup"
}

A default value fallback for is recommended, editors is used in the example below

In the project to be embedded it will look like this:


//...
const groupName = process.env.COGNITO_USER_GROUP_NAME || 'editors';
const region = process.env.AWS_REGION; // set up by serverless itself
const cognitoUserPoolId = process.env.COGNITO_USER_POOL_ID; // needed for auth

const app = express();

// Enable CORS for all endpoints
app.use(cors());
app.use(bodyParser.json({strict: false}));

const config = {
  app,
  groupName,
  cognitoRegion: region,
  cognitoUserPoolId,
  auth: 'automatic',
  env: process.env,
};

cognitoServerAuth(config);
//...

On serverless.yml you will need to give some extra permissions to the lambda

provider:
  # permissions required for THIS LAMBDA (not the user of the API)
  iamRoleStatements:
    - Effect: Allow
      Action:
        - cognito-idp:ListUsers
        - cognito-idp:AdminListGroupsForUser
      Resource:
        # This incantation is required for the lambda to have permission to access the cognito user pool
        - "arn:aws:cognito-idp:${self:provider.region}:*"