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

@hstm-labs/forge-run

v0.3.8

Published

Post-deliver stage that updates root `package.json` scripts and optionally runs the dev stack for verification.

Downloads

1,919

Readme

@hstm-labs/forge-run

Post-deliver stage that updates root package.json scripts and optionally runs the dev stack for verification.

Purpose

  • Script updates: Add or fill in infra:up, db:create, db:seed, build, start, and run:all so the delivered project has a consistent dev workflow.
  • Optional execute: When config.runVerify.execute is true, run the script sequence and HTTP health checks (for CI or local smoke tests).

Auth mode (Keycloak vs local users)

Run-verify supports two auth modes so dev deployment matches how the application authenticates users:

  • authMode: 'oidc' — Application uses an IdP (OIDC/OAuth) and has a local user table that caches IdP data plus app-specific values. For dev, we include Keycloak (or another IdP) in the deployment and seed it with users that match the users seeded in the database. Use this when the app relies on IdP for authentication and you want to test the full flow (Keycloak + DB users aligned).
  • authMode: 'local' (or unset) — Application only supports authentication with application-owned users (local users table, no IdP). Keycloak is not included in the dev deployment. Use this when there is no IdP and users exist only in the app DB.

Set in forge.config.json:

{
  "runVerify": {
    "execute": true,
    "authMode": "oidc"
  }
}

When authMode is 'oidc', the stage adds scripts keycloak:up and keycloak:seed and uses a run:all order: infra up → keycloak seed → db create → db seed → build → start. The Keycloak seed step should align users with those from db:seed (same identities/attributes). When authMode is 'local' or omitted, no Keycloak scripts are added.

Config

| Option | Type | Description | |--------|------|-------------| | runVerify.execute | boolean | If true, run script sequence and health checks after updating scripts. | | runVerify.healthUrls | string[] | URLs to GET for health checks (default: localhost:3000/health). | | runVerify.authMode | 'oidc' | 'local' | IdP + Keycloak in dev vs local users only; see above. |

Public API

  • RunVerifyStage — Pipeline stage (depends on deliver).
  • updatePackageJsonScripts(rootDir, layoutName, authMode?) — Add default scripts to root package.json.
  • getDefaultScriptsForLayout(layoutName, authMode?) — Get script map for a layout and optional auth mode.
  • runScript, runScriptSequence, healthCheck, healthCheckWithRetry — Execution helpers.
  • Types: RunVerifyReport, ScriptRunResult, HealthCheckResult, RunVerifyAuthMode.