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

devel-info

v1.0.0

Published

Collect dev-related data in node.js apps (environment, cluster, process, system, request...)

Downloads

3

Readme

devel-info

Collect dev-related data in node.js apps (environment, cluster, process, system, request...) and show it in pretty format. May be useful for overall application state overview in production environments.

devel-info looks like a charm)

Installation

Use npm to install it to your app:

npm install --save devel-info

Usage

As node server or connect/express middleware

Run following script:

var develInfo = require('devel-info');

// for node server
require('http')
    .createServer(develInfo())
    .listen(8011);

// or for connect middleware
require('connect')()
    .use(develInfo())
    .listen(8011);

and navigate to http://127.0.0.1:8011/devel-info after application starts.

Additional initialization should be applied on cluster setup to collect information about workers:

var develInfo = require('devel-info');
var cluster = require('cluster');
develInfo.initCluster(cluster);

if (cluster.isMaster) {
   // master init
} else {
   // workers init
}

See example for working solution.

As standalone function

var develInfo = require('devel-info');

develInfo(function(err, data) {
    if (!err) {
        console.log(data);
    }
});

Options

develInfo([config], [callback], [clientRequest|])
  1. config could be an object with following options:

    • url — url for devel-info page (default: '/devel-info').
    • type — output format (default: 'html' for using as middleware or 'json' for using with callback)
    • sections — info sections collected from node app environment (default: ['package', 'proc', (config.custom), 'request', 'request.parsed', 'request.headers', 'request.headers.cookie', 'os', 'process', 'process.env', 'os.networkInterfaces'])
    • custom — custom object with any data to show in devel-info page (default: undefined)

    config could be String or Array and will be treated as sections option in this case. Also, config argument could be skipped — the defaults will be used.

  2. callback is a function which called on info gathering finish. Use it if you want to control all this stuff manually ;)

  3. clientRequest is a node object which represents an in-progress request. Used for collecting request-related information and make sense only when using callback.

Demo

Run directly from your application root for quick demonstration:

node node_module/devel-info/example

License

MIT license