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 🙏

© 2024 – Pkg Stats / Ryan Hefner

ycplmon

v1.1.2

Published

Makes all inclusions of string CODExxxxxxxx unique.

Downloads

4

Readme

ycplmon

This tool is used to create unique CPLs (Code-Place-Locators) across your source code.

CPL is string like CODEnnnnnnnn it can be part of other string.

Why

It's just a very fast and convenient way for me to find where some error message or log message was emited.

Without this when you see 'Failed to open XXXX file' you will then waste some time to find out where is the code which opens file.

But when you see 'CODEXXXXXXXX Failed to open XXXX file' you just search for 'CODEXXXXXXXX' in all your git project and instantly know where it was opened.

You can do that instantly even if the user sends you screenshot and you can't just copy-and-paste your error message.

Installation

npm i -g ycplmon
yarn add -g ycplmon
pnpm i -g ycplmon

How this works:

  • Suppouse all your code is in "src" folder

  • Anywhere in your code write CODEnnnnnnnn where nnnnnnnn- are any 8 digits

  • run "ycplmon fix src" or "ycplmon2 fix src"

  • This command replaces all non-unique CPLS with unique ones. Now all this tags will have unique codes

  • Now log this CPLs, print them or save to DB

  • And when you want to find the code that emmited them - just search through all your code base for specific CPL.

Tips and tricks

  • If you want to generate some files use ``CODE${'00000000'}` ` .