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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@salayna/shrimp-cli

v0.6.2

Published

Yet another Project Builder

Readme

Shrimp CLI

I'm a newbie in Golang, I'm still figuring out things so you'll probably have a lot to say about this, so feel free publish issues

Install

Just building a binary file

To install it locally you can just run the following command go build -o ./bin/shrimp after cloning the project sources

Running the app

With the local installation you can run the cli with this command ./{path/to/your/binary/file} comment: <> And with the global installation you can just run shrimp.

The arguments

this part is deprecated, while the arguments are still there I'm not satisfied with them so by the release of V1 these will drastically change

  • -n || --name: is the name/directory of the project
  • -l || --language: is the language of the project to be chosen from a specific set of configuration files, stored in the configs folder
  • -f || --file: Not Implement yetis if you wanna created a project from a configuartion file (like for a one time project)
  • -v || --verbose Not Implement yet
  • -v || --version Not Implement yet

Adding configuations

The configurations files will be stored in the configs folder at $HOME/.shrimp. All of them must be written in JSON here is an example of configuration files

{
  "directories": {
    "src": {
      "baseDir": "internal",
      "subDir": [
        "cli"
      ]
    },
    "scripts": {
      "baseDir": "pkg"
    },
    "deployments": {
      "baseDir": "deployments"
    },
    "test": {
      "baseDir": "test"
    },
    "docs": {
      "baseDir": "docs"
    }
  },
  "commands": {
    "git": {
      "base": "git",
      "arguments": ["init"]
    },
    "golang init": {
      "base": "go",
      "arguments": ["mod", "init"]
    }
  },
  "files": {
    "LICENSE": {
      "name": "LICENSE",
      "directory": "./"
    },
    "Main": {
      "name": "main.go",
      "directory": "./"
    },
    "ReadMe": {
      "name": "README.md",
      "directory": "./"
    }
  }
}