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

@beecode/msh-cli

v2.1.0

Published

MicroService Shell helper

Downloads

57

Readme

Build Status codecov GitHub license
NPM

msh-cli

Micro-service helper: cli

Idea

This tool was created to be used in specific environment. We are using it for managing multiple microservice project that are sitting next to each other in one parent project.

example: Project name = Simple Project (short sp)

sp                      <parent project>
├── auth                <microservice>
├── node-common         <shared library>
├── type-definitions    <shared typescript definitions>
├── .gitignore          <parent project is ignoring all microservice projects>
├── .msh
├── docker-compose.yml

First feature added was the git bach commands and it was used to easily and quickly clone all repositories and perform functions like git status and git pull. Because of this we decided to have certain naming convention.

We chose to have a prefix for every project which takes first letters of the projects name Simple Project => sp, so for authentication microservice we get sp-auth. But when we clone it strip the prefix.

Configuration

configuration is stored in the file .msh located at the root of your project. You can generate init config file by calling msh -i.

PROJECTS=["auth","node-common","type-definitions",..]
GIT_TEAM=TeamName
GIT_PROJECT_PREFIX=tn

LOG_LEVEL=error

CMD_GIT_ENABLED=true
CMD_NPM_ENABLED=true

Also you can use .msh-user (next to the .msh) at your root dir to store user override values like

[email protected]
GIT_PASSWORD=*****

Features

  • git
    • status
    • fetch
    • pull
    • clone
  • npm
    • install

git

Perform git commands on all project specified in .mas config file under PROJECTS. All commands are executed asynchronously.

  • status - Get git status for all microservice projects

  • fetch - Perform git fetch for all microservice projects

  • pull - Perform git pull for all microservice projects

  • clone - Clone all microservice projects. If GIT_PROJECT_PREFIX is set the project prefix is going to be striped for all projects.

npm

  • install - Run npm -i for all project listed in PROJECTS.

Help

Usage: msh [command]

Command:

   -i | --init             Initiate .msh config file with default values

   -g | --git [option]
       options:
          clone            Clone all project
          pull             Pull all projects
          fetch            Fetch all projects
          status           Get status for all projects

   -n | --npm  [option]    Run npm i in all containers
       options:
          install          Run npm i for all projects

   -v | --version          Display cli version

   -h | --help             Display this help