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

is-connected-to-systemd-journal

v1.0.0

Published

Determine if stdout or stderr is connected to the systemd journal

Downloads

6

Readme

Determine if the current process is connected via stdout or stderr to the systemd journal.

Build Status

NOTE ABOUT UBUNTU 16.04

This module checks the environment variable JOURNAL_STREAM which was introduced in systemd v231. As of this writing, Ubuntu 16.04 is using systemd v229, which means that this module will always return false in Ubuntu 16.04.

It is suggested that, in Ubuntu 16.04 and other systems with systemd < 231, set an environment variable for your process and use that to determine whether to log to systemd's journal or to stdout.

if (isConnected.sync() || process.env.VARIABLE_I_SET_TO_TRIGGER_JOURNAL) {
  // Log to the journal
}

Installation

npm install --save is-connected-to-systemd-journal

Usage (synchronous)

const isConnected = require('is-connected-to-systemd-journal')

let log = null;
if (isConnected.sync()) {
  // set up logging to require('systemd-journald') or other
}
else {
  // set up logging to some other sink (like console.out)
}

isConnected.stdoutSync() // is stdout connected to the journal
isConnected.stderrSync() // is stdout connected to the journal
isConnected.sync() // same as isConnected.stdoutSync

Usage (async)

const isConnected = require('is-connected-to-systemd-journal')

isConnected((err, connected) => {
  let log = null;
  if (connected) {
    // set up logging to require('systemd-journald') or other
  }
  else {
    // set up logging to some other sink (like console.out)
  }
})

isConnected.stdout(cb) // is stdout connected to the journal
isConnected.stderr(cb) // is stdout connected to the journal
isConnected(cb) // same as isConnected.stdoutSync