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

@ttoss/logger

v0.3.13

Published

Simple environment agnostic logger

Downloads

17

Readme

@ttoss/logger

Simple environment agnostic logger.

Motivation

Often, for debugging some piece of code, developers use console.log for it. When the application goes for production, some of these logs still appears, most because they forget to clear these logs. These package solves this, providing some levels of log that are emitted based on the environment of the application.

Log Levels vs Environments

How to use

Just instantiate the logger, providing the isDev value configuration and start to use:

// createLogger.ts

import { Logger } from '@ttoss/logger';
import { config } from 'dotenv';

config();

export const createLogger = Logger(process.env.DEV === 'true');

// randomFile.ts

const logger = createLogger('randomFile');

logger.warn('This will emit an warn on console');

logger.error('This will emit a log of type error on console');

loggger.info('This will emit a simple log on console');

If you not pass any parameter to Logger, it gonna considers to be in dev environment:

// createLogger.ts

import { Logger } from '@ttoss/logger';

// In dev environment, gonna log everything
export const createLogger = Logger();