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

@overture-stack/persona

v1.1.1

Published

🚧 user profile and identity management

Downloads

11

Readme

Slack

usage

persona's main export is an express router, to be included in a parent application. an example instantiation is included in examples/app.ts, which is hooked up to the npm start script mentioned in the dev section below.

getting started

  • npm i --save @overture-stack/persona
  • add the required environment variables, documented in .env.schema
import * as express from 'express';
import * as cors from 'cors';
import createServer from '@overture-stack/persona';

const start = async () => {
  const port = 3232;
  const app = express();

  app.use(cors());

  app.use(
    await createServer({
      ego: {
        required: false,
        accessRules: [
          {
            type: 'deny',
            route: ['/', '/(.*)'],
            role: ['admin', 'user'],
          },
        ],
      },
      schemas: {
        User: {
          fields: {
            email: 'String',
            interests: ['String'],
          },
          collection: 'users',
        },
      },
      tags: {
        User: ['interests'],
      },
    }),
  );

  app.listen(port, () => console.log(`Listening on port: ${port}`))
};

start();

vault

persona supports vault integration by default. the USE_VAULT environment variable will determine whether or not persona should try to use vault to connect to mongo, or if it should use explicitly provided connection credentials.

migrations

depending on your usage the mongo instance backing persona may need migrations. persona provides migration support in the form of the persona-scripts.

persona migrations require the global installation of the migrate-mongo package, npm i -g migrate-mongo. for more information visit https://www.npmjs.com/package/migrate-mongo.

after installing persona, run persona-scripts migrate --args "<<migrate-mongo commands>>" from your project root to perform migration tasks. migrate-mongo commands include status, up, down, and create <<migration name>>

persona-scripts migrate will create a migrations/migrations directory structure in the root directory of your project.

environment variables

see .env.schema for details on environment variables

dev

  1. install dependencies
$ npm i
  1. make sure mongo is running
$ mongod
  1. start server (defaults to port :3232)
npm start
  1. personal is now running and you can access it http://localhost:3232/graphql

docker

To get a local instance of persona running you can use the docker compose file. This will start mongo and persona in docker.

$ docker-compose up --build

If you need a different port you can use the API_HOST_PORT env variable

$ API_HOST_PORT=3232 docker-compose up --build