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

service-probe

v0.1.6

Published

The 'service-probe' returns information about the service (such as dependecies)

Downloads

13

Readme

service-probe

NPM

NPM version David David NPM license Omniref flattr

The 'service-probe' returns information (such as dependecies) about the first parent module in the path hierarchy.

Take a look to the TODO if you want to help towards the next steps.

Installation

Node Dependencies

Add following line to your project dependencies

"service-probe": "0.1.x",

then hit

npm install

Require module

var probe = require('service-probe');

Usage

[property] means the property is only set it a value was found

Probe Object

The Probe is an extention of the Root Object provided by the root-finder package

service-probe adds following properties to the Root Object:

  • status: 'OK' if the probe was processed without problems, 'ERROR' otherwise
  • timestamp: the time at which the probe was generated
  • hostname: the name of the host
  • pid: the process id
  • ip: the ip address from the network adapter
  • version: the version of the package
  • [version_hash]: the parsed content of .git/HEAD
  • dependencies: the parent module's dependencies as array of objects formated as follows

Dependecy Object

  • type: string - specifies it is a Node ('node') or Bower ('bower') dependency
  • production: boolean - specifies it is a production dependency
  • path: string - path to the dependency
  • name: string - the name dependency module
  • version: string - the dependency module's version
  • [description]: string - the dependency module's description
  • [keywords]: array of strings - the dependency module's keywords
  • [homepage]: string - the dependency module's homepage
  • [repository_url]: string - the dependency module's repository_url
  • [engines_node]: string - the dependency module's supported version of node

Access Values

Access the values with the point notation:

var probe = require('service-probe');

// get parent module's name
probe.name

// get root path
probe.path

// get list of dependencies
probe.dependencies