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

mirrorneuron-web-ui

v1.2.23

Published

MirrorNeuron web UI dashboard.

Readme

MirrorNeuron Web UI

mn-web-ui is the React/Vite browser interface for inspecting MirrorNeuron runtime state, job history, job graphs, events, dead letters, and raw manifest submissions through mn-api.

Quick Start

Install dependencies and start the development server:

npm install
export MN_ENV=dev
cp .env.example .env.dev
npm run dev

Run local checks:

npm run lint
npm test -- --run
npm run build

Default local URL:

http://localhost:55173

Details

Notes

  • Start mn-api before using live runtime screens.
  • The default API base URL is /api/v1.
  • Set MN_WEB_API_TOKEN when connecting to a protected API instance.

Configuration

Configuration is defined in config/definitions.ts and loaded by config/node.ts. The loader uses this precedence:

real environment variables
> .env.${MN_ENV}
> .env
> built-in safe defaults

MN_ENV defaults to dev when unset. dev and development load .env.dev, test loads .env.test, and prod or production load .env.prod when it exists. Production does not require any .env file.

Development example:

export MN_ENV=dev
cp .env.example .env.dev
npm run dev

Test example:

export MN_ENV=test
npm test -- --run

Production example:

export MN_ENV=production
export MN_HOME=/var/lib/mirrorneuron
export MN_LOG_LEVEL=info
export MN_API_HOST=0.0.0.0
export MN_API_PORT=8080
export MN_WEB_API_BASE_URL=/api/v1
npm run build

Do not commit real .env files. Use .env.example for documented placeholders only, and provide secrets such as MN_WEB_API_TOKEN through deployment environment variables.