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

emo2

v0.0.6

Published

Convert human unfriendly strings to emoji in your terminal

Downloads

6

Readme

Emo

Convert human unfriendly strings to emoji in your terminal

What? Why?

There are a lot of human unfriendly strings out there, for instance, UUIDs and SHA1s.

When you have to work with a couple of these strings, it's manageable; most programmers I know see f985dab7704a and remember that as "the one that starts with f9." And tab completion helps. But when you start to have tens or hundreds of these strings, it starts to get messy, and we lose the ability to quickly look at some output and see what node/commit/container/image is being referenced.

Installation

emo requires nodejs. Once you've installed node (which now comes bundled with npm) you can install emo by running

npm install -g emo2

Usage

You can pipe stdout to emo, and emo will replace human unfriendly strings with emoji, and store that data to ~/.emo.

git log | emo
docker ps | emo

Then you can look stuff up in either direction, like so:

emo f985dab7704a
emo 🐤
docker kill $(emo 👾)

gif

Options

When piping, you can add -s to have emo add spacing equivalent to the length of the string being replaced.

gitlg | emo -s

When you see an emoji and want to know what the hell it's called, you can get node-emoji's name for it with the -i option

emo 📠 -i

There's also a sample mode, which just returns random emoji, which you can "use" like so:

emo sample 10

Caveats

  • Unique to you, each emoji is assigned randomly. It'd be cool if they were computed/encoded from the string, but I couldn't figure out a good way to do that without needing to make the replacement many emoji long.
  • Some emoji look very similar
  • My regex for detecting "human unfriendly strings" leaves a lot to be desired
  • You probably shouldn't use this for anything serious, though I'm having a hard time thinking how one even would
  • Only tested on a Mac

created by zach schwartz