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

laxative

v1.2.0

Published

πŸ’Š One config, whole stack: laxative conducts poops (frontend) and septic (backend) into a single MVP.

Readme

πŸ’Š laxative npm version ci license mit

One config, whole stack. laxative conducts poops (frontend) and septic (backend) into a single MVP β€” from one poops.json.

It's a conductor, not an engine. poops bundles and renders; septic serves the API, generates the forms, and feeds the static build. laxative just runs them together, on one origin. It reimplements nothing.

Why

You already have the organs:

  • poops β€” the bundler + static-site generator.
  • septic β€” config β†’ SQLite + REST API + generated forms + the poops build bridge.

They already share poops.json. What was missing: running them as one thing β€” the API and the static site on the same host, so a generated <form> POSTs to /api on the origin that served the page. That's laxative.

Use

npm i -D poops laxative
laxative init      # scaffold poops.json (markup + styles + scripts + septic + a form) + the pages
laxative dev       # site + /api on one origin; poops watches + live-reloads behind it
laxative build     # septic build (DB β†’ markup + forms) β†’ poops compile β†’ dist/
laxative serve     # production: serve dist/ + /api + /uploads from one process

septic comes along as laxative's own dependency β€” you never install it separately. poops is an optional peer you install yourself; PORT overrides the default 3000.

Full reference: stamat.info/laxative.

The one-origin server

laxative serve/dev boots septic's app (mounting /api/*, /uploads) and serves the poops-built site behind it. Same host, same port:

GET  /                β†’ dist/index.html         (poops output)
GET  /api/messages    β†’ septic REST             (JSON or, for HTMX, HTML)
POST /api/messages    β†’ the generated form's target
GET  /uploads/…       β†’ septic media

A frontend-only project (no septic block) still works β€” laxative just serves the static site.

The whole loop

Define a resource once in poops.json β†’ septic makes the table + API + form partial, poops renders the page that includes it, laxative serves both together. Define messages β†’ get a working, validated contact form on a static page, wired to its own endpoint.


Yes, still a fan of toilet humor. πŸ’©πŸš½πŸ’Š

MIT Β© Stamat