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

edi-devops

v0.8.6

Published

The team's single point of access to the essential suite of apps, tools, and documentation for efficiency, effectiveness, and success!

Readme

Our EDI DevOps spans multiple analysts, developers, and consultants with support from their Technical PM, me. I am thinking it better to consolidate our KB/HOWTO, dashboards, monitors, reporting and tools into one portal. And for the past 8 years, I have been advocating the use of VS Code as a replacement over the proprietary Studio IDE. It is apparent with the 2024 release that now is a good time to do that.

In steps Code Server to mitigate and provide a centralized solution to resolve its complexity for having to disparately install on a variety of remote endpoints. Also, there are numerous activities needed to work off the host CLI, so providing a number of self "helpers" to Xterm.js consoles is beneficial toward the team's overall technical maturity.

As a final objective, I would like to promote the team's activities off the home page, suitable for guest browsing too, that can provide the latest news and events out of this space. Some may be generated programmatically while others could be a post by the team (moderated by its admins).

screenshot

Linux host setup

SystemD

Configure the portal service for automatic startup in production mode:

$ cp env-example .env
# edit .env to meet your needs
$ sudo cp devops.service /etc/systemd/system/
$ sudo systemctl daemon-reload
$ sudo systemctl enable devops
$ sudo systemctl start devops

Apache

After your SSL directives within your site httpd configuration, append:

    # set Proxy atttributes
    ProxyRequests Off
    ProxyBadHeader Ignore
    ProxyPreserveHost On
    # harden as needed
    <Proxy *>
        Order deny,allow
        Allow from all
    </Proxy>
    SSLProxyCheckPeerName Off
    SSLProxyVerify None

    # allow websocket connections into Nuxt app & Code Server session
    RewriteEngine On
    RewriteCond %{HTTP:Connection} Upgrade [NC]
    RewriteCond %{HTTP:Upgrade} WebSocket [NC]
    RewriteRule "^/devops/_nuxt/(.*)" "ws://localhost:3000/devops/_nuxt/$1" [P,L]
    # configure for a new VS Code Server instance -> user session
    RewriteCond %{HTTPS} On
    RewriteRule "^/devops/code/(0-9)+/([a-z0-9]+)$" "/devops/code-server/$1/?workspace=/home/$2/.local/share/code-server/User/Workspaces/$2-devops.code-workspace"

    # proxy Code Server endpoints -- as many concurrent sessions as needed
    <Location "/devops/code-server/6501/" >
        ProxyPass http://localhost:6501/
        ProxyPass "ws://localhost:6501/"
        ProxyPassReverse http://localhost:6501/
    </Location>

    # Nuxt portal endpoint
    <Location "/devops">
        RequestHeader set X-Forwarded-Proto "https"
        ProxyPass http://localhost:3000/devops
        ProxyPassReverse http://localhost:3000/devops
    </Location>

Initial Setup

Make sure to install the dependencies:

$ npm install

Development Server

Start the development server on http://localhost:6500:

# prefix HOST= and/or PORT= as overrides
$ npm run dev

Production Mode

Build the application for production:

$ npm run build

Locally preview production build:

$ npm run preview

Check out the Nuxt deployment documentation for more information.

Change Log of major events

08-Jul-2025 switch Node.js v20 (Iron) to active LTS v22 (Jod)

In essence, Node.js 22 refines and expands upon the features of Node.js 20, with a focus on performance, developer experience, and enhanced interoperability between module systems. While Node.js 20 was a significant release, Node.js 22 represents the latest stable version with the most recent performance gains and feature set.