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

systeminformation-api

v0.0.4

Published

Expose systeminformation as REST APIs

Downloads

7

Readme

System Information API

This is a thin wrapper around systeminformation to expose it as a REST API.

Dependencies

You have to have node.js and npm setup. Uses express to create minimal web service and minimist to process command line argument. For testing I rely on mocha/chai/chai-http. All the dependencies are automatically installed by npm - see below.

How to Use it

Download

Clone or download it from git hub:

git clone https://github.com/asokolsky/systeminformation-api.git

or just use npm to download and install it:

npm i systeminformation-api

Build

Run in the shell in the directory where you cloned systeminformation-api:

npm install

Test

in the shell:

node test

Run

and then in the shell

node index.js

Finally, point your browser http://localhost:3000/api/systeminformation/cpu

Command Line

node index.js [{-p|--port}:<portnumber>] [-z|--zip] [-h|--help] [-v|--version]
  • {-p|--port}:<port> - specifies port on which the service will listen for incoming HTTP connections
  • -z|--zip - will force express to use gzip encoding - experimental, not for production
  • -h|--help - display command line spec
  • -v|--version - show package version

REST APIs Supported

Only HTTP GET is supported.
The URIs start with /api/systeminformation followed by:

  • empty string - returns systeminformation package version
  • time - returns time JSON
  • system
  • bios
  • baseboard
  • cpu
  • cpuFlags
  • cpuCache
  • cpuCurrentSpeed
  • cpuTemperature
  • mem
  • memLayout
  • diskLayout
  • battery
  • graphics
  • osInfo
  • versions
  • shell
  • users
  • fsSize
  • blockDevices
  • fsStats
  • disksIO
  • networkInterfaces
  • networkInterfaceDefault
  • networkStats
  • networkConnections
  • currentLoad
  • fullLoad
  • processes
  • dockerContainers
  • dockerAll
  • getStaticData
  • getDynamicData

For a full description of the underlying functionality see the systeminformation documentation.

Deploy

Here are the Best Practices.

Debugging

The package relies on (almost standard) debug package. Command line to enable this app trace on Windows (powershell, default in vscode):

$env:DEBUG='siapi';node .\index.js

Try this to learn more about express:

$env:DEBUG='*';node .\index.js

Credits

systeminformation by Sebastian Hildebrandt

TODO

If you have an opinion or ideas on the below list - please do tell.

Logging

Decide on the logging facility to use: https://strongloop.com/strongblog/compare-node-js-logging-winston-bunyan/

Package it as a Service

https://github.com/coreybutler/node-windows

https://github.com/tallesl/qckwinsvc

Package it as a Docker Image

https://nodesource.com/blog/8-protips-to-start-killing-it-when-dockerizing-node-js

DONE

Adopt debug facility

Use debug package instead of console.

Publish it in npm

DONE: https://www.npmjs.com/package/systeminformation-api

Using gzip encoding

Followed the best practices suggestions, adopted optional gzip encoding. Did not benchmark the impact though.