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

@simsa/smoke-verifier

v0.18.1

Published

Conclave AI smoke verification — runs Playwright user-flow checks against a live deploy URL after autofix push, catches runtime regressions that build+test verify cannot (e.g. missing env vars, paused backend, broken third-party calls).

Readme

@simsa/smoke-verifier

Playwright-driven smoke checks against a live deploy URL after autofix push. Closes the gap between "build + tests pass" and "user-facing flows actually work".

Why

Conclave's existing autofix loop verifies:

  • pnpm build succeeds
  • pnpm test passes
  • the deployed app actually loads

That last one is the gap. Real failures we've seen in the wild:

  • Supabase free-tier auto-paused → TypeError: fetch failed on every API call (eventbadge, 2026-05-07)
  • Env var missing on Vercel after migration
  • Third-party API quota hit
  • DB migration not applied to remote
  • next.config.mjs change broke the prod build but not the local one

A 30-second Playwright smoke against the real deploy preview catches all of those before the verdict ships to the user.

Quick start

Add .conclave/smoke.yaml to your repo:

# Smoke checks for eventbadge — runs after every autofix push, against
# the deploy preview URL.
steps:
  - name: home page loads
    goto: /
  - expect-status: 200
  - expect-text:
      text: "이벤트 만들기"

  - name: create-event flow loads
    goto: /events/new
  - expect-status: 200
  - expect-text:
      selector: "form"
      visible: true

Conclave's autofix pipeline reads it (when present) and runs the steps against the freshly-deployed preview URL after git push. The result becomes part of the cycle-end report:

✅ Build + tests passed (cycle 1/3)
✅ Smoke verified live (3/3 steps)
   ✓ home page loads (200)
   ✓ create-event flow loads (200)
   ✓ form visible

Or, if smoke fails:

✅ Build + tests passed (cycle 1/3)
❌ Smoke broken on live deploy
   ✗ home page loads — got 503, want 200
   ⊘ create-event flow loads (skipped after halt)
→ Cycle marked as deploy-broken — handing back to human

Step kinds

| Step | Effect | |---|---| | goto: <path> | Navigate to <base-url><path> | | expect-status: <N> | Most-recent goto must have returned N | | expect-text: { text, selector?, visible? } | Selector contains text, OR page contains text | | click: <selector> | Playwright page.click(selector) | | fill: { selector, value } | Playwright page.fill | | wait-for: <selector> | page.waitForSelector (with optional timeoutMs) |

Config keys

stepTimeoutMs: 15000      # per-step timeout (default 15s)
continueOnFailure: false  # halt on first failure (default) vs collect all
userAgent: "Conclave AI smoke verifier"
steps: [...]

AI Slop check (v2)

Beyond pass/fail steps, smoke verifier scans deployed HTML for known LLM placeholder leakage:

  • // TODO: implement left in source
  • Lorem ipsum placeholder text
  • your-api-key / your-secret literal strings
  • <INSERT_X> markers
  • I would suggest..., This is a placeholder AI commentary

Hits surface in the report alongside step failures. Useful for catching worker-generated changes that "look complete" but contain placeholder content.

Wiring into autofix-pipeline

Hook is opt-in via .conclave/smoke.yaml presence. When file is absent, smoke verification is skipped silently and the cycle behaves as today (build + tests only).

Why not just use Vercel deploy preview's built-in checks?

Vercel doesn't run e2e tests on previews — it just serves the static build. Smoke verifier specifically tests the live runtime behavior of the user-facing flows that are most often broken by autofix.