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

gle

v1.0.3

Published

Global Log Engine: Environment-agnostic debugging & logging utility

Downloads

1,037

Readme

GLE

Global Log Engine: Environment-agnostic debugging & logging utility

GLE is a logging and debugging utility which allows for easy application/library debug log output when flagged by environment variables.

Inspired by debug, but with additional support for more environments like:

  • NodeJS
  • Browsers
  • React-Native

Installation

Run the following to install: npm install gle --save.

Usage

Import one of the two following functions to start logging:

import { createLog, log } from "gle";

const logContext = createLog("my-app:core");
logContext("test log", "some info");

// Or

log("my-app:core", "test log:", "some info");

createLog builds a log function with the context already defined. It is generally better for performance, as well. log does everything on the fly, and requires a context in every call.

A context is a way to group logs together into some kind of logical "area" of your application or library.

To be able to view these logs, the correct environment variable must be specified.

Displaying logs in the browser

To enable logging for a context in the browser, you can use something like the following:

localStorage.debug = "app:*";

Later:

import { createLog, log } from "gle";

const logContext = createLog("app:websocket");
logContext("connecting socket");

Which will display a log like the following in the browser's console:

app:websocket connecting socket +0ms

Displaying logs in NodeJS

To enable logging for a context in a NodeJS app, set the DEBUG environment variable:

DEBUG=app:* node index.js

Later, after building:

import { createLog, log } from "gle";

const logContext = createLog("app:db");
logContext("connecting database");

Log flags

The debug environment value can be made up of several different types of patterns:

  • A single context: my-app:some:context
  • Multiple contexts: app:core,app:net
  • A Negated context: -app:test
  • A combination: -app:test,app:init
  • Wild cards: app:*
    • Multiple: app:*,system:*
    • Anywhere: app:test,system:*:core
    • Negated: -system:*