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

sbas

v0.3.0

Published

Loyal CLI shortcuts

Downloads

1

Readme

Sebas

Create aliases to commands or tasks(JS/Sh files) using files.

Installation

# For npm users
npm i -g sbas
# For yarn users
yarn global add sbas

Usage

Create a .sebas folder in your $HOME directiory. Then add your commands by creating files that has the shortcut name and contain the intended command:

echo "rpm-ostree status" > status

Then use it anywhere like this:

sbas status

If the command isn't found inside .sebas folder, sebas will try to run the command as is:

sbas ls # where ls command isn't inside .sebas folder
# will show files like ls does

Using folders to group commands

mkdir os && cd os
echo "rpm-ostree status" > status

and use it like this:

sbas os status

JS tasks

you can add js files inside .sebas they will be executed when called:

echo "console.log(\"Hi :)\")" > hi.js

and use it like this:

sbas hi
Hi :)

sh files

you can run sh files the same way as js ones:

# inside .sebas folder
echo "touch hi.js && ls" > yo.sh

and use it like this:

sbas yo
hi.js # etc...

Change .sebas directory

Add an environmental variable called SEBAS_DIR it will be used by default.

Contributing

  1. Fork it!
  2. Create your feature branch (git checkout -b my-cool-feature)
  3. Commit your changes (git commit -am 'add my feature')
  4. Push to the branch (git push origin my-cool-feature)
  5. Create a new Pull Request