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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@cthru/ctxcmdr

v0.2.0

Published

Path-contextual @cthru/cmdr executor. Lets you run commands upstream in your path with cwd as local folder

Readme

ctxcmdr

I know, I know.. terrible name. This is a utility app I'm sharing with the people I work with. When I have some more time, I'm going to make it better and put it in a proper project.

Setup

To install npm install -g @cthru/ctxcmdr After installation it will prompt you for a command name / script folder name. Just stick to the default (dev)

Usage

For many projects I have a /dev folder containing node cli utilities to help automate the project. Usually, I would just go to the root of the project and do dev/log to run the log watching script. However, if I am in some subfolder.. I have to first go to my project root to run the utility script or deal relative paths. Nobody likes to do ../../dev/log

This utility lives globally under the command you selected (dev) by default. If you run dev log it will look for the first /dev folder in the hierarchy that contains a log script and will then execute that script

If you run dev without arguments, it will find all the /dev folders up the folder tree and list all the executables (chmod +x) files. Start typing to filter and selecting a task will execute it.

Now I can be wherever in my project and do dev log without having to hunt for the script

That is all this does.

Needless to say, if you decide to use a different command - say d - then it will look in .../d/* for scripts rather than in .../dev/*

Don't look at the code - it is horrible. You have been warned. If do though, and you squint, you may see a quick example implementation of generators as used to find the script folders and script files.

Create a script folder

dev --init-script-folder will create ./dev and do npm init -y

Create a script

dev --create-script <scriptname> will create a new @cthru/cmdr style script after doing the same as --init-script-folder