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

Votesy

v0.0.1

Published

Merendi Network's Votesy

Downloads

7

Readme

Votesy

Install

git clone
npm install

Edit .env file at the root to change the mongo string and other settings. the .env file is only read locally. On production, the environment variables are used instead (change those on heroku)

Run

node multithread.js

Generate the compiled JS slug for production push

Before you push to prod, the JS files need to be minified in a single file, and the static files that changed need to be uploaded to the CDN.

To do so, run the server locally, and in the browser go to /api/sys/slug

The node console will output the progress.

This will generate the minified JS file, and will create a slug.json file at the root which will be read by the server on prod.

Push to heroku

git add --all
git commit -m "..."
git push heroku master

Questions?

If you have any question about the code, please contact the original developer: [email protected] (skype: j.loutre)