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

@jenkins-cd/diag

v0.0.2

Published

Jenkins client-side diagnostics

Downloads

18

Readme

Jenkins client-side Diagnostics

Installation

npm install --save @jenkins-cd/diag

logger(category)

Get a LOGGER for the specified category.

var LOGGER = require('@jenkins-cd/diag').logger('sse');
 
// Log messages etc . See below.

error(message [, other-args])

var LOGGER = require('@jenkins-cd/diag').logger('sse');

LOGGER.error('Invalid SSE event message format.', event);

Error logs are always logged, so no configuration needed here.

debug(message [, other-args])

Currently, this module uses the enabled package for logging debug messages.

NOTE: One slight terminology difference between this package and the enabled package is that this package uses the term "category" (log "category") where enabled uses the term "namespace"/"name". Aside from that, everything else is the same.

var LOGGER = require('@jenkins-cd/diag').logger('sse');

LOGGER.debug(`SSE event ${event.jenkins_channel}/${event.jenkins_event}:`, event);

Please see the enabled (and env-variable) docs for how to turn on/off debug logging in the Browser.

isDebugEnabled()

Returns true if debug logging is enabled for the category associated with the logger instance.