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

spawn-pq

v1.0.0

Published

nodejs [pq](https://github/com/iximiuz/pq) spawner _(native rust binding on the way)_

Downloads

3

Readme

spawn-pq

nodejs pq spawner (native rust binding on the way)

Requirements

cargo install pq --git https://github.com/iximiuz/pq

Usage

Do not use this. It's for testing with pq in preparation for the native binding.

CLI

pq.js "query" parameters

Wrapper

var init = require('spawn-pq')
var args = process.argv.slice(2);
var pq = init(args);
    pq.stdout.pipe(process.stdout);
    process.stdin.pipe(pq.stdin);

Test

cat test/inputweb   | ./pq.js "/[^\\s]+[^\\[]+\\[([^\\]]+)]\\s+\"([^\\s]+)[^\"]*?\"\\s+(\\d+).*/ | map { .0:ts \"%d/%b/%Y:%H:%M:%S\", .1 as method, .2 as status_code } | select count_over_time(status_code[3s]) | to_promapi" --interval 1s
cat test/inputagg   | ./pq.js "/([^\\s]+)\\s(\\w+)\\s(\\d+)\\s(\\w+)\\s(\\w+)/ | map {.0:ts \"%Y-%m-%dT%H:%M:%S\", .1 as name, .3 as country, .4 as job, .2 as age} | select min(age) without(name,job) | to_promapi" --interval 1s
cat test/inputcount | ./pq.js "/[^\\[]+\\[([^\\s]+).+?]\\s+\"([^\\s]+)[^\"]*?\"\\s+(\\d+)\\s+(\\d+).*/ | map {.0:ts \"%d/%b/%Y:%H:%M:%S\", .1 as method, .3 as content_len} | select count_over_time(__line__[1s]) | to_promapi"