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

overwrite-system-logs

v1.0.2

Published

Library with functionality that overwrites all console methods to give a more precise format. Configuration based on winston dependency.

Downloads

341

Readme

Overwrite System Logs

Library with functionality that overwrites all console methods to give a more precise format. Configuration based on winston dependency.

How to use

overwrite-system-logs-tests
├── package.json
└── src
    ├── index.js
    └── index.ts
// src/index.js
require('overwrite-system-logs').overwriteSystemLogs();

const logsTest = () => {
    const helloWorld = 'hello world from overwrite-system-logs';
    console.log({ helloWorld });
    console.log('Test message');
};

logsTest();
// src/index.ts
import { overwriteSystemLogs } from 'overwrite-system-logs';

overwriteSystemLogs();

const logsTest = (): void => {
    const helloWorld: string = 'hello world from overwrite-system-logs';
    console.log({ helloWorld });
    console.log('Test message');
};

logsTest();

Output:

2021-12-15T15:34:47.433Z INFO [ src/index.js 5:5 | object ]: {"helloWorld":"hello world from overwrite-system-logs"}
2021-12-15T15:34:47.434Z INFO [ src/index.js 6:5 | string ]: Test message

2021-12-15T15:34:50.065Z INFO [ src/index.ts 7:5 | object ]: {"helloWorld":"hello world from overwrite-system-logs"}
2021-12-15T15:34:50.066Z INFO [ src/index.ts 8:5 | string ]: Test message

Log output elements and structure

<dateToISOString> <INFO|WARN|ERROR> [ <folder/file{.js|.ts}> <line>:<position> ]: <mensaje>

Configuration

It is necessary to provide an environment variable called LOG_LEVEL and assign it a value, in case it is not defined, the library takes by default the level of log info

Log levels:

  • error
  • warn
  • info
  • debug

Ordered from most important to least important. If the value defined in LOG_LEVEL is none of these, an exception will be thrown.

If you want the objects to have a pretty-print, just provide another environment variable called LOG_PRETTY that represents the space argument. see documentation

Dependencias

This logger works using as dependency the Winston library link