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

statusline

v0.1.13

Published

Universal status line implementation in Node.JS

Downloads

37

Readme

statusline

This project is in development

Statusline is modular status line for use with i3bar, tmux, etc.

Screenshot

My config

Usage

Installation

sudo npm install -g statusline

Using within i3bar

In ~/.i3/config find status_command and set it to statusline i3status.

Configuration

Your default config will be stored in: ~/.statusline.conf when you run statusline i3config for the first time.

Features

  • [x] Package manager (for installing packets inside users home, npm based)

Example block: https://github.com/statusline/statusline-block-time

To installe block, run:

statusline install block-time

Note: Do not type statusline- on the beggining of package name.

  • [x] Block API for writing custom blocks (able to handle click events)

Blocks available so far: ip, load, time, date, battery

I was thinking about giving options object to package function and getting back object with default output and object for templating engine, for user defined text.

If you are developing block, keep in mind Promise may get replaced with EventEmmiter at a point in time...

  • [ ] Middleware API for writing middleware that can alter final output

  • [ ] Command API for creating output for different applications, for example tmux status...

Only i3status available. It is built in.

  • [x] Config system

Something like this for now

{
	"blocks": [
		{
			"name": "battery",
			"backgroundColor": "#000",
			"color": "#fff",
			"customOptions": {
				"battery": "BAT0"
			}
		}
	],
	"middleware": [
		{
			"middleware": "powerlineSeparator"
		}
	]
}
  • [ ] Async rendering and error handling

Package naming

When creating package, it is important to follow naming convention.

NPM package name should be: statusline-[block/middleware/command]-[name] (for example statusline-block-time).

Credits

nemanjan00