New Case Study:See how Anthropic automated 95% of dependency reviews with Socket.Learn More
Socket
Sign inDemoInstall
Socket

white-logger

Package Overview
Dependencies
Maintainers
1
Versions
8
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

white-logger

a very simple browser and node logger with only one dependency

0.2.1
Source
npm
Version published
Weekly downloads
0
Maintainers
1
Weekly downloads
 
Created
Source

white-logger

A very simple nodejs and browser logger with only one dependency.

🚧 NOTICE: white-logger is currently in beta. There may be frequent updates that are not backwards compatible. Please keep an eye on our update docs.

We expect to release a stable version of 1.0.0 in 02/2023.

feature

  • Only one dependency. Use Luxon for dealing with dates and times.
  • Pretty print.
  • Native TypeScript.
  • Circular safe.

install

npm i white-logger

useage

nodejs

use typescript or ESM

import { nodelogger as logger } from "white-logger/node";

logger.normal("normal-level", "normal reported.");
logger.info("info here", "something reported.", {
  hello: "world",
});
logger.warn("notice", "something warnning.", ["foo", "baz"]);
logger.err("oops!", "something error!");

You will get like this in your console.

log preview img

You can also give __filename to the second parameter to get relative path output from your project root dir.

import { nodelogger as logger } from "white-logger/node";

logger.info("some info", __filename, "i am here!");

And you will get like this. Easy to find out the problem, right?

filename preview img

By default, white-logger does not write log to files. If you want to do this, please configure some setting like this.

import { nodelogger as logger, configLogger } from "white-logger/node";
import path from "path";

// By setting the logPath option, white-logger will write the log to files automatically.
configLogger({
  logPath: path.resolve(process.cwd(), "logs"),
});

// Will be written to <project_root>/logs/<timestamp>_info.log
logger.info("some-info", "something reported.");

Depending on the level, the logs will be written to different files.

  • logger.normal will write to <timestamp>_normal.log
  • logger.info will write to <timestamp>_info.log
  • logger.warn will write to <timestamp>_warn.log
  • logger.err will write to <timestamp>_err.log

Timestamp will change from day to day. So, the logs are output to a different file each day.

You can also only pass a relative path, white-logger will resolve it to your project root directory automatically.

configNodeLogger({
  // Same as above, logs will write to <project_root_dir>/logs
  logPath: "logs",
});

use CommonJS

const { nodelogger } = require("white-logger/node");

nodelogger.normal("normal-level", "normal reported.");

You can also import with a name of your choice.

const mylogger = require("white-logger/node").nodelogger;

mylogger.normal("normal-level", "normal reported.");

browser

You can use white-logger in any framework. Like vue or react.

// Please note that the esm module is in esm directory.
import { browserlogger as logger } from "white-logger/esm/browser";

logger.normal("normal-level", "normal reported.");
logger.info("info here", "something reported.", {
  hello: "world",
});
logger.warn("notice", "something warnning.", ["foo", "baz"]);
logger.err("oops!", "something error!");

Open your console and you can see the results.

browser preview img

You can use configBrowserLogger function to configure your browser logger.

import { configBrowserLogger } from "white-logger/esm/browser";

configBrowserLogger({
  mode: "production",
  targetUrl: undefined,
  storagePrefix: undefined,
});

By default, browser logger running in development mode.

  • In development mode, browser logger will print log to console.
  • In production mode, will NOT print to console, but will do diffrently depending on the targetUrl or storage config.
    • If targetUrl defined, browser logger will post log to given url by use fetch api.
    • If storage defined, browser logger will save log into localStorage with given prefix string.
    • For more information, please see this document.

configuration

node logger

export type NodeLoggerConfig = {
  logPath: string | undefined; // full or relative path to your logs directory
  logDateFmt: string; // Luxon format string
  filenameDateFmt: string; // Luxon format string
};

// default value
let __config__: NodeLoggerConfig = {
  logPath: undefined,
  logDateFmt: "yyyy'-'LL'-'dd HH':'mm':'ss Z",
  filenameDateFmt: "yyyy'-'LL'-'dd",
};

About Luxon format string, please see this Luxon document

  • logPath: The path of directory that white-logger will write log to.
  • logDateFmt: The format of the date being printed to the console.
  • filenameDateFmt: The format of the date before being inserted into the output file.
  • For more infomation please see nodelogger document

browser logger

export type BrowserLoggerConfig = {
  mode: "development" | "production"; // browser logger mode
  logDateFmt: string; // luxon date format string
  targetUrl: string | undefined; // fetch post url
  storagePrefix: string | undefined; // localStorage item key prefix
};

// default value
let __config__: BrowserLoggerConfig = {
  mode: "development",
  logDateFmt: "yyyy'-'LL'-'dd HH':'mm':'ss Z",
  targetUrl: undefined,
  storagePrefix: undefined,
};

About Luxon format string, please see this Luxon document

  • mode: browser logger mode. For more information on the differences between the two modes of blogger please see this document.
  • logDateFmt: The format of the date being printed to the console.
  • targetUrl: Post url in production mode.
  • storagePrefix: localStorage prefix in production mode.
  • For more information, please see this document

Why is it call White logger?

"Any color you want, so long as it is Black."

So, White logger.

Keywords

logger

FAQs

Package last updated on 09 Feb 2023

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts