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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@mauikut/hh200

v0.0.1

Published

Statically-checked DSL for testing HTTP servers

Readme

hh200 lang

CI

Contributing

The project is in ideation phase (Update late 2025: slowly transitioning to a hazily more committal phase; expect target release date sooner rather than later!). DRAFT.md is where I stash my thoughts. hh200/ works if you want to play with what I got so far.

stack install
bats php-dev-server integration.test
# stack.yaml

snapshot:
  url: https://raw.githubusercontent.com/commercialhaskell/stackage-snapshots/master/lts/24/26.yaml

Features

The following defining features sum up hh200 in trade-off terms.

1. Fail fast (compromising test percentage)

Well-functioning system-under-test is the only thing that should matter; we're dodging the need for skipping cases in test scripts.

2. Regex, random, time batteries (compromising binary size)

hh200 comes integrated with a full expression language BEL evaluator.

See also

LR grammar

hh200 grammar builds on hurl's, which we're going to just trust to be consistent with its parser implementation (a handwritten recursive descent parser).

Syntax decision notes

URL fragments agree with https://hurl.dev/docs/hurl-file.html#special-characters-in-strings

Development system dependencies

  • bats (latest npmjs package: 1.13)
  • php (latest debian stable: 8.4)

Build Dependencies

Notable aspects:

  • Uses bel-expr expression language
  • Integrates with Language Server Protocol (lsp) for IDE support
  • Includes both parsing (parsec) and lexer/generator tools (alex/happy)

Development

Developing a rule in the grammar is an activity of conservatively editing src/L.x and src/P.y at the following sites.

-- src/L.x
tokens :-
    ...

data Token =
    ...
  deriving (Eq, Show)
-- src/P.y
%token
    ...  { ... }

rule : ...
stack purge  # rm -rf .stack-work
stack run
ghciwatch --command "stack repl" --watch . --error-file errors.err --clear  # fast feedback loop!
stack exec hh200 -- --version +RTS -l -RTS  # generates .eventlog

Modelling parallel test users

Haskell distincts parallelism (executing computations simultaneously to improve performance) from concurrency (managing multiple independent computations that may interact, such as through I/O or shared resources).

hh200 doesn't try to speak in the same granularity as haskell or any parallelism-supporting languages. We could reexport our host language's semantics with our syntax; this option is always option for future implementations of hh200. But for now when we say "HTTP server test with parallel users", we are thinking about a specific semantics for the following example program:

#! ["user1", "user2"] row

"download image.jpg"
GET https://fastly.picsum.photos/id/19/200/200.jpg?hmac=U8dBrPCcPP89QG1EanVOKG3qBsZwAvtCLUrfeXdE0FI
HTTP [200 201] ("/downloads/img-{{row}}.jpg" fresh)