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

saylo

v0.5.1

Published

use logger.log instead of console.log and you can mute unmute (turn on or off) console.log calls

Downloads

100

Readme

Saylo (turn on/off console.log)

code coverage version downloads license

Installation

To install this npm package do

npm i -P saylo

Usage

Then from your javascript files import either logger or log directly with:

//var logger = require('saylo');
import logger from 'saylo';
import { log } from 'saylo';

Then you can replace your console.log with either log() or logger.log():

import logger from 'saylo';

const a = 'Hey there how are you?';
const b = function() { 'any type goes' };
logger.log('my log output is: ', a, b); // 'my log output is: ', 'Hey there how are you?' , function () {'any type goes'}

logger.turnOff();
logger.log('my log output is: ', a, b); // no output

logger.turnOn();
logger.log('my log output is: ', a, b); // 'my log output is: ', 'Hey there how are you?' , function () {'any type goes'}

Control through env vars

Before you load the logger module, you can set the environement variable SAYLO_LOGGING like:

process.env.SAYLO_LOGGING=1
// or
process.env.SAYLO_LOGGING=0

and it will turn the logger on or off. You can also store these in a .env file. In which case the import 'dotenv/config'; statement will load them for you. (You need to npm i -P dotenv for this to work.

Roadmap

Next step:

  • Create logging sets and subsets, which you can turn on or off for finer control
    logger('level1').log('my string to log');
    logger('level2').log('my string to log');
    // or
    logger1.log('my string to log');
    logger2.log('my string to log');