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

fiveo

v1.0.3

Published

Node Inspector API Sugar

Downloads

6

Readme

fiveo

Build Status

Fiveo Demonstration https://youtu.be/q9c3ZXq75Kg

A tiny JavaScript library to add some sweetness to Node's core inspector module. Adds some key missing features:

  • Adding the ability to start the inspector via the SIGNAL method using ANY PORT and not just 9229. Opens up the possible debug applications and workflows tremendously.
  • STOPPING the inspector instance using the SIGUSR2 signal (will stop both sessions started with SIGUSR2 and the native SIGUSR1). It's likely that leavning the inspector listening (production environments...) is a bad idea.

Installation

$ npm install fiveo

Usage

fiveo simply needs to be required in your code.

Example:

require('fiveo');
// The rest of your code...

Environment Variables

When running through Node.js, you can set a few environment variables that will change the behavior of the debug logging:

| Name | Syntax | Purpose | Examples | |-----------|--------|-----------------------------------------|----------------| | INSPECT | [hostname:port] | Declares which host:port you want the inspector to listen on. | 9230 or localhost:9230

Note: The default value for INSPECT is localhost:9229.