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

besonders-logger

v1.0.1

Published

## Why? ### Simple & powerful syntax ```typescript const { WARN, LOG, DEBUG, VERBOSE, ERROR } = Logger.setup( Logger.INFO, { prefix: '[DB]' } // (optional) );

Downloads

51

Readme

besonders-logger

Why?

Simple & powerful syntax

const { WARN, LOG, DEBUG, VERBOSE, ERROR } = Logger.setup(
    Logger.INFO, 
    { prefix: '[DB]' } // (optional)
);

DEBUG(`test=${1}`, extra, {objects})
LOG(`test=${1}`)
if (VERBOSE.isEnabled) VERBOSE(`won't be run:`, heavyComputation())
WARN(`test=${1}`, extra, {objects})
throw ERROR(`msg logged & returned as Error, plus formatted:`, extra, {objects})

... while still preserving correct log location

  • in devtools, you see the correct line as origin
  • in node.js you can print the source location in grey (optional)

(optional) Concise relative times

Screenshot (only with custom devtoolsFormatters enabled)

Installation

Add besonders-logger to a Javascript/Typescript project:

pnpm add besonders-logger
yarn add besonders-logger
npm add besonders-logger

# (optional) install vscode snippets:
# Linux script, source: .vscode/install-snippets.sh
pnpm run besonders-install-snippets
# or copy manually from the source repo

Usage

And in any file you want to use logger:

// protip: use `logsetup` snippet

import { Logger } from "@ztax/logger/src";

const { WARN, LOG, DEBUG, VERBOSE, ERROR } = Logger.setup(Logger.INFO); // eslint-disable-line no-unused-vars

Change log-level

const { WARN, LOG, DEBUG, VERBOSE, ERROR } = Logger.setup(Logger.DEBUG); // eslint-disable-line no-unused-vars
const { WARN, LOG, DEBUG, VERBOSE, ERROR } = Logger.setup(Logger.WARN); // eslint-disable-line no-unused-vars
//... or any other level

console.groupCollapsed mdn

LOG.group('init', () => {
	LOG('do something')
	doSomething()
	DEBUG('something done')
})

The inner function will always be executed - also when the loglevel would be filtered, in which case there is no group around the inner logs.

Temporarily override loglevel for a single line

Pro tip: add a pre-commit hook to disallow committing

VERBOSE.force("foo") // will be printed in any loglevel

Temporarily log everything

window.FORCE_DISABLE_LOGLEVEL = true