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

wesignup

v1.0.5

Published

## Install Download and install Node.js >= 7.7.1 then run ``` yarn install ```

Downloads

1

Readme

Protocol Signup

Install

Download and install Node.js >= 7.7.1 then run

yarn install

Init database

Set up and run migrations directly from the terminal using Sequelize CLI. Here is how to do:

yarn exec -- sequelize db:migrate --url 'mysql://username:password@hostname:port/database'

If your local db server does not support SSL, change the ssl option to false in db/config/config.json.

To seed the database with seed users:

yarn exec -- sequelize db:seed:all --url 'mysql://username:password@hostname:port/database'

Seed data can be added at: db/seeders

To start a-fresh:

yarn exec -- sequelize db:migrate:undo:all --url 'mysql://username:password@hostname:port/database'

Example one-liner

yarn exec -- sequelize db:migrate:undo:all --url 'mysql://root@localhost:3306/faucet' && yarn exec -- sequelize db:migrate --url 'mysql://root@localhost:3306/faucet' && yarn exec -- sequelize db:seed:all --url 'mysql://root@localhost:3306/faucet'

Configure

Copy .env.example to .env and edit as needed. (.env-admin.example for faucet-admin)

Run

Faucet:

env $(tr "\\n" " " < .env) yarn start-dev # or just start, if you don't want nodemon

Faucet-Admin

See the readme in /admin

Docker

A Dockerfile is supplied. You will need to configure the app with environment variables. See the file .env.example for a full list of what you will need.

When running the Docker image locally, you will probably need to bind your mysqld to not only localhost but also the IP used in Docker's network. You can then specify this IP in DATABASE_URL.

You can build and start the Docker image like this:

BRANCH="$(git rev-parse --abbrev-ref HEAD)"
docker build -t WeYouMe/wesignup" .
docker run -it -p 5678:5678 --env-file=.env "WeYouMe/wesignup"

Debugging

VSCode:

Add the following to .vscode/launch.json configurations array:

  {
    "type": "node",
    "request": "launch",
    "name": "nodemon",
    "runtimeExecutable": "${workspaceRoot}/node_modules/nodemon/bin/nodemon.js",
    "program": "${workspaceFolder}/bin/www",
    "restart": true,
    "sourceMaps": true,
    "outFiles": [],
    "console": "integratedTerminal",
    "internalConsoleOptions": "neverOpen",
    "args": [
        "--ignore src",
        "| bunyan -o short"
    ],
    "envFile": "${workspaceFolder}/.env",
  }

Testing

The test command will run three other scripts in sequence: static analysis (eslint), unit and integration tests (jest), and dependency security check (nsp).

You do need to supply dummy values for some required environment variables. Do so like this:

env $(tr "\\n" " " < .env.example) yarn test