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

hlidskjalf

v0.4.2

Published

A Terminal User Interface for monitoring Turborepo tasks, built with Ink

Readme

hlidskjalf

NPM Version NPM Last Update GitHub License

A Terminal User Interface for visualizing Turborepo tasks, built with Ink.

Usage

Add to your root package.json:

{
  "scripts": {
    "dev": "hlidskjalf"
  }
}

Then run it:

pnpm dev

Options

| Option | Description | | --- | --- | | filter | Include specific workspaces (--filter=web). Append ... for transitive dependencies (--filter=web...). | | order | Sort by alphabetical or run (--order=run). Defaults to alphabetical. | | title | Custom title for the header (--title="My App"). Defaults to Hlidskjalf. | | theme | Colour theme (--theme=niflheim or --theme=ice). Defaults to bifrost. | | metrics | Show CPU and memory usage per workspace. Defaults to false. | | watch | Re-discover workspaces when package.json files change. Defaults to true; disable with --watch=false. |

Themes

Named for the realms of Norse cosmology, to match the all-seeing high seat the tool is named after:

| Theme | Alias | Mood | | --- | --- | --- | | bifrost | — | Default - electric purples, sky blues, and starlight whites. | | niflheim | ice | Ice — glacial blues, frost-white highlights. | | muspelheim | fire | Fire — molten oranges, ember golds. | | yggdrasil | earth | Earth — mosses, leaf-greens, bark greys. |

Each realm also answers to its elemental alias, so --theme=ice is the same as --theme=niflheim.

Configuration

Persist any of the options above. Create a hlidskjalf.config.ts at the repo root:

import { defineConfig } from 'hlidskjalf'

export default defineConfig({
  order: 'run',
  metrics: true,
  filter: ['web...'],
  theme: 'niflheim',
})

defineConfig is optional — a plain export default { ... } works too. hlidskjalf.config.js / hlidskjalf.config.mjs are also recognized. The .ts form needs no build step: it's loaded directly via Node's type stripping (Node ≥ 22.18).

Alternatively, add a hlidskjalf key to your root package.json:

{
  "hlidskjalf": {
    "order": "run",
    "metrics": true
  }
}

Precedence is CLI flags → hlidskjalf.config.*package.json key → defaults, so a flag always wins over a stored value.

Watching

While running, hlidskjalf watches your packages, apps, and services directories. When a workspace's package.json is added, removed, or changed it re-runs discovery: new workspaces start automatically and removed ones are stopped and dropped from the dashboard. Pass --watch=false (or set watch: false) to turn this off.

Controls

| Key | Action | | --- | --- | | / | Move the selection between workspaces | | s | Stop the selected workspace (or start it again if stopped) | | r | Restart the selected workspace | | c | Clear the logs for the selected workspace | | PgUp / PgDn | Scroll the log panel up / down a page | | q | Quit |

License

MIT