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

@furystack/onboard

v1.0.30

Published

A helper tool to instantly setup dozens of microservices with ease

Downloads

42

Readme

onboard

A helper tool to instantly setup dozens of microservices with ease

Installation

You can install the tool globally with npm install @furystack/onboard -g

Init and customize a new config

Once installed, you can create a new config file with the onboard init command. This will create a default (and nearly empty) onboard-config.json config file in the current working directory. You can edit that file to customize your dev environment. You can also use auto completition in IDEs that supports it (e.g. VS Code)

Input and output dirs

Input can be used for input artifacts (e.g. database dumps) that are neccessary for the service initialization. The services will be cloned to the output directory. Both paths should be absolute.

Service list

The services should contain a list of services that you want to install. Service installs can run parallelly but the install steps will be executed in a series. If one step fails, the install process will be aborted. There is a fixed set of steps available at the moment:

  • DockerInstall - Installs a Docker container (if it's not already installed). Requires Docker.
  • GitClone - Clones a GIT repository (optionally pulls it if already exists). Requires GIT client.
  • BowerInstall - Install dependencies via Bower. Requires Bower.
  • NpmInstall - Executes the NPM Install command. Requires NPM
  • NpmScript - Executes a specific NPM script
  • MongoRestore - Restores a specific dump file (should be relative to the input directory)
  • AddToPm2 - Adds a specific file to the PM2 Process Manager An example install can look like: GitClone -> NpmInstall -> NpmScript (build) -> AddToPm2