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

dot-logs

v1.1.0

Published

A winston implementation to make logs easy

Downloads

6

Readme

Dot-logs

npm GitHub Workflow Status npm bundle size Commitizen friendly semantic-release: angular

This library aims to bring you an easy way to log stuff both in your console and .log files.

Installation

$ npm i dot-logs

Usage

import DotLogs from 'dot-logs';

const log = new DotLogs();
log.info('my awesome log');

Note

At the moment we only support Typescript and ESModules, but we are currently working on giving support for CJS as well.

Check this issue for more information.

There are 6 log levels built-in, all available at your instance. They all expect only one parameter

  • .error()
  • .warn()
  • .info()
  • .http()
  • .debug()
  • .verbose()

Take in mind that DotLogs is a singleton class so you can instance it only once in your application and then reference it everywhere you need it.

All logs will be stored in a /logs/all.log file on a /logs folder at the root of the project; if the /logs folder does not exists before the first log, Dot-Logs will create it for you.

You can configure the path where Dot-Logs will store the .log files at the constructor:

const log = new DotLogs('dist/logs')

There are two other files that will be created, the info.log and error.log files containing all the logs for those levels.

It will also catch and log uncaughtException events and store them on the exceptions.log file.

By default the log format is timestamp log-level: message and the timestamp YYYYMMDD HH:mm:ss.

License

MIT License.

Copyright (c) 2022 Facundo Carbonel / LogIt