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

containerized

v1.0.2

Published

A microlibrary to detect whether Node.js runs inside a Docker container or not

Downloads

1,810

Readme

npm version Build Status Coverage Status

Containerized

  • Detect whether your Node.js process runs inside a Docker container or not
  • Detection is based on existence of Docker-specific cgroups
  • Well tested (aiming at 100% line, function, statement and branch coverage)
  • Works with all Node.js versions >= 0.10.x.
  • Tested in 0.10.x, 4.x, 5.x, 6.x.

Usage

npm install containerized

Node.js versions 0.12, 4.x, 5.x, 6.x, ...

var containerized = require('containerized');

if (containerized()) {
	console.log('I am running inside a Docker container.');
} else {
	console.log('I am NOT running inside a Docker container.');
}

In Node.js 0.10.x

Up until node 0.10.x, containerized offers only async way of fetching whether the process is containerized in a container or not.

var containerized = require('containerized');

containerized(function(err, result) {
	if (result === true) {
		console.log('I am running inside a Docker container.');
	} else {
		console.log('I am NOT running inside a Docker container.');
	}
});

For synchronous interface in Node <= 0.10, wrap it in deasync module:

var deasync = require('deasync');
var containerized = deasync(require('containerized'));

// then you can:
if (containerized()) {
	console.log('I am running inside a Docker container.');
}

Licence

MIT.

Contribute?

You're welcome! Make sure you keep an eye on the tests.