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

dev-env-status-check

v1.0.0

Published

Check the availability of common Node development environment dependencies

Downloads

20

Readme

dev-env-status-check

Check the availability of common Node development environment dependencies like node, npm, git, and others.

npm travis standard conduct

About

When helping a new programmer set up their computer for the first time it can be difficult to debug their system.

This module intends to be a high-level approach to checking which dependencies are correctly set up on a computer.

It's written with node, which may seem a little silly (what if they don't have node yet?!), but the intent is to use this inside Electron apps.

The first electron app to use this module is dev-env-status, a simple app that shows the availability of each tool and how to install it if needed.

Work in progress

There are still some improvements that need to be made before ready for use. Contributions are welcome.

Planned improvements (PRs welcome!)

This module needs to be tested and adapted for use on both linux and windows.

There are ways this module can be smarter about detecting system dependencies. For example: what if a macOS user doesn't have gcc yet?

For now this only checks node, npm, and git. It would be cool to accept arbitrary commands.

Check out the dev-env-status repo for additional improvements.

Command-line tools that are checked:

  • node
  • npm
  • git

Each tool returns an object with:

  • exists – boolean
  • path – absolute path for the command
  • version – version of the command

Operating system information

You're also provided information about the computer's operating system:

  • arch – return value of os.arch()
  • platform – return value of os.platform()
  • release – return value of os.release()
  • namemacOS Sierra for example

Install

npm install --save dev-env-status-check

Usage

var check = require('dev-env-status-check')

var stream = check()

stream.on('data', function (data) {
  if (data.type === 'os') {
    console.log('operating system info:', data)
  } else {
    console.log('status of ' + data.command + ':', data)
  }
})

Each data event returns an object with information about the computer.

If the object has a type property of os, it contains information about the operating system:

{
  type: 'os',
  arch: 'x64',
  platform: 'darwin',
  release: '16.1.0',
  name: 'macOS Sierra'
}

If the object has a type property of command, it contains information about one of the commands. For example:

{
  type: 'command',
  command: 'node',
  exists: true,
  path: '/Users/sdv/.nvm/versions/node/v6.9.1/bin/node',
  version: '6.9.1'
}

Contributing

Contributions are welcome! Please read the contributing guidelines first.

Conduct

It is important that this project contributes to a friendly, safe, and welcoming environment for all. Read this project's code of conduct

Changelog

Read about the changes to this project in CHANGELOG.md. The format is based on Keep a Changelog and this project adheres to Semantic Versioning.

Contact

License

ISC