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

@dung95/test123

v1.6.3

Published

🚀 lightweight logger • level based filtering and tagging • weighs in at 500 bytes

Downloads

3

Readme

missionlog NPM version Build status Coverage Status Bundlephobia dependencies Status

Lightweight logger with an extensible configuration. Supports level based filtering and tagging. Filtering keeps your logs readable and uncluttered while tagging makes them searchable.

Features

  • Small footprint, around 500 bytes with 0 dependencies
  • Filter by level, ERROR > WARN > INFO
  • Filter by tag, 'security' | 'whatever'
  • Log callback is extensible from console to cloud
    • Style terminal output with chalk
    • Send JSON to a cloud service like Loggly
    • Log strings and objects to the console
    • Combine any of the above based on env
  • API mirrors console.log, logs objects and supports rest parameters
  • Works reliably with node or any browser through a bundler
  • Includes TypeScript definitions so no need for external @types

Install

npm install missionlog

Initialize

Tags typically refer to a subsystem or component like 'security' or FooBar.name.When missionlog is initialized, tags can be assigned a level. A message is logged when its level is greater than or equal to its tag's assigned level.

// var log = require('missionlog').log;
import { log, LogLevel } from 'missionlog';

/**
 * initialize missionlog
 * @param config JSON which assigns tags levels. An uninitialized,
 *    tag's level defaults to INFO.
 * @param callback? handle logging whichever way works best for you
 */
log.init(
  { transporter: 'INFO', security: 'ERROR', system: 'OFF' },
  (level, tag, msg, params) => {
    const prefix = `${level}: [${tag}] `;
    switch(level) {
      case LogLevel.ERROR:
        console.error(prefix, msg, ...params);
        break;
      case LogLevel.WARN:
        console.warn(prefix, msg, ...params);
        break;
      case LogLevel.INFO:
        console.info(prefix, msg, ...params);
        break;
    }
  });

Usage

import { log, tag } from 'missionlog';

// the imported value "tag" is populated with YOUR tags!
log.error(tag.security, 'not authorized', statusCode);

// but if you prefer simply use strings
log.warn('transporter', 'Evil twin detected!');

// filtered since security's log level ERROR is greater than INFO
log.info(tag.security, 'login successful');

// also filtered since system's level is OFF
log.error(tag.system, 'eject the warp core', error);

// updates tag levels on the fly
log.init({ loader: 'ERROR', system: 'INFO' });

// disable logging by clearing the callback
log.init();

Advanced Usage

Create an instance with its own tags and callback.


import { Log, tag } from 'missionlog';

const myLog = new Log().init(
  { loader: 'INFO', security: 'ERROR' },
  (level, tag, msg, params) => {
    console.log(`${level}: [${tag}] `, msg, ...params);
});

myLog.info(tag.security, 'login successful');