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

@simpleworkjs/app-stack

v1.0.0

Published

Shared app-stack helpers for the theta42 apps — unified build_info + static-module mounting.

Downloads

2,521

Readme

@simpleworkjs/app-stack

Shared app-stack helpers for the theta42 apps (sso-manager-node, proxy, jump-host). The verifiable, low-risk extractions from the "feel the same" UI stack.

What it provides

  • createBuildInfo({ version, buildCommitPath, cwd }){ buildVersion, buildHash, buildYear }. The unified build-info shape. Prefers a baked commit file (docker images have no git), falls back to git rev-parse --short HEAD, then 'unknown'. sso + proxy already used this shape; jump-host used { commit, version } and is normalized onto it.
  • mountStaticModules(router, { root, deps, publicDir?, moduleMaxAge?, publicMaxAge?, staticMiddleware? }) — the static-mounting convention all three apps duplicate: each vendor dep at /static-modules/<dep> (7-day cache) from <root>/node_modules/<dep>, and the app's own assets at /static (1-hour cache) from <root>/public (or an explicit publicDir).

What it deliberately does NOT include

The higher-risk UI surface — top.ejs/bottom.ejs (nav gating differs per-app), app-base.js (sso's Promise form uses $.isFunction, removed in jquery 4), val.js (host/target rules are proxy-specific), and the jquery 3↔4 / ejs 6↔3 major-version alignment — diverges per app and has no render-test coverage. That's a separate, explicit decision, not an autonomous extraction.

Install

npm install @simpleworkjs/app-stack

Usage

const { createBuildInfo, mountStaticModules } = require('@simpleworkjs/app-stack');
const { version } = require('../package.json');
const path = require('path');

// utils/build_info.js
module.exports = createBuildInfo({
  version,
  buildCommitPath: path.join(__dirname, '../.build_commit'),
  cwd: __dirname,
});

// routes/render.js (or routes/index.js)
mountStaticModules(router, {
  root: path.join(__dirname, '..'),
  deps: ['bootstrap', 'mustache', 'jquery', '@fortawesome', 'moment', '@popper', 'jq-repeat'],
});

License

MIT © William Mantly