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

codenotch-cli

v1.0.31

Published

A CLI tool for code management

Readme

Getting started

To use the commands codenotch-cli or cn

npm run build npm link

When there is a change, you need to relaunch npm run build

Runtime

The CLI will automatically download the latest version runtime the first time it's needed or anytime cn runtime install or cn runtime update is used. Since the package is private at the moment, you'll need to login via an interactive browser prompt.

By default the CLI installs the runtime in a .codenotch folder in the user home directory ($HOME / USERPROFILE). This behaviour can be changed by setting CODENOTCH_PATH in the .env file.

Manual install

You can also get the runtime manually here: https://github.com/EchinoHub/service-core/releases/ Then you can either find/create a .codenotch in your home directory or set the CODENOTCH_PATH to where you put the runtime.

Runtime requirements

You need to have NodeJs installed and available on the PATH for the runtime to work properly.

.npmrc

We need a npm token to get the private package codenotch-react from npm. At the moment we use a npm file that we copy on build to the project. This token is not valid to get others private packages, meaning it will also prevent you from installing other codenotch packages We need to fin a real solution to this or simply make the codenotch-react package public