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

moar

v0.0.9

Published

$PAGER abstraction for node

Downloads

32

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Maintainers

russfrankrussfrank

Keywords

Readme

moar

a pager for nodejs.

what?

Look, I'm not happy about this either. The problem is that there isn't a good way to page data cross platform. Also, I don't know how your $PAGER works, or if it's going to be okay with the data I'd like to give it.

Thus, I present moar. It will (eventually) support most of the features less supports. But instead of being written in C, it's written in javascript so we can all hack on it and have fun with it and benefit from the awesome cross platform ansi-to-win32-console-api magic that the libuv folks have slaved over.

why not just pipe to $PAGER

Look, I tried to get this to work for a while. Trust me, it wasn't my first instinct to re-implement $PAGER's functionality in javascript. But without using either a native module or internal node APIs, it's just not possible; and even with the internal APIs it's ugly (would probably have to hit a file first).