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

sal

v1.2.1

Published

Trying to save you from configuration. This project is not meant to be everything, but a nice place to start.

Downloads

12

Readme

Sal

Trying to save you from configuration. This project is not meant to be everything, but a nice place to start.

Some information you should know before starting:

Setting up the port for production right now is hardcoded to 5000 becuase I wanted this project to work with Dokku from the start.

Please refer to the notes in config.js and src/server/index.js

Running this application for development

npm install
sal -rd

Deploying with Dokku

After you have set up your Dokku server please follow these instructions

Using the sal commandline tool:

npm install sal -g
-------------------------- Sal --------------------------
          use "sal --help" to see all options
              https://github.com/rtorr/sal
---------------------------------------------------------

Options:
  --run, -r   Run a sal application - `sal --run <path>`
  --test, -t  Run your tests
  --new, -n   Create a new Sal project - `sal --new <path>`
  --dev, -d   Set process.env.NODE_ENV to dev
  --prod, -p  Set process.env.NODE_ENV to production
  --kill, -k  Kill all Sal servers (This maps to pm2)
  --help      Show help

Features:

By default you get React (JSX), ES6, Typescript, Expressjs, Mocha, and Karma.

VS Code

Meant to be used with vscode, with these settings. More to come on this.

  • Supports build and test vscode commands

Imgur