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

shurl-debug

v1.0.4

Published

Utility Tool

Readme

Shurl Debugging Utility Tool

Codeship Status for camscottFS/URL-Debug

The .env file is located your root directory.

You'll need to add the following to the .env file:

DEBUG = true
DEBUG_CONSOLE = true
DEBUG_MSG_LOG = true

You can automatically install the Debugging tool as an NPM Package like this:

npm install shurl-debug --save

The files will then be saved in node_modules

To turn off the debugging tool can simply edit the .env file and change DEBUG = true to DEBUG = false

To prevent debug messages from appearing in the console you must change DEBUG_CONSOLE = true to DEBUG_CONSOLE = false.

To disable logging of the .msg() method you must change DEBUG_MSG_LOG = true to DEBUG_MSG_LOG = false.

Below is an example of what you can expect the log to generate when the debugging tool is enabled:

Event at 15:05:19 @ server.js on line 30
SUCCESS
Server active on port 3000

Event at 15:05:22 @ app.js on line 15 GET:/status
SUCCESS
Server status is healthy!

Event at 15:05:27 @ app.js on line 41 GET:/urls
SUCCESS
Read all URLs

Event at 15:06:52 @ app.js on line 65 GET:/urls/:id
SUCCESS
Read URL by ID

This debugger will save log files to a folder called logs in your the root directory of the application.