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

loug

v1.0.2

Published

Console for debugging messages, errors and warnings in projects that are in development.

Downloads

7

Readme

Loug

Console for debugging messages, errors and warnings in projects that are in development.

Installation

$ npm install --save loug

Add the production key in your package.json.

{
  "name": "testing",
  "version": "3.2.1",
  "description": "description testing",
  "main": "index.js",
  "scripts": {
  },
  "keywords": [
  ],
  "dependencies": {
  },
  "production": false    //=> This key
}

The key production is boolean type, true is production.

When the key is set to true the messages are not displayed. The opposite happens when it is false.

Usage

"production": false

var loug = require('loug');

loug("Hello")
//=> Hello
loug.warn("an advert")
//=> an advert
loug.ignore("Any argument or message")
//=> Any argument or message

"production": true

var loug = require('loug');

loug("Hello")
loug.warn("an advert")
loug.ignore("Any argument or message")
//=> Any argument or message

API

log(msg...)

Logs the message as if you called console.log

error(msg...)

Logs the message as if you called console.error

warn(msg...)

Logs the message as if you called console.warn

info(msg...)

Logs the message as if you called console.info

dir(msg...)

Logs the message as if you called console.dir

ignore(msg...)

Logs the message as if you called console.log. Logs the message in production and development.

Ignore all

Ignore the 'production' key and enable log, error, warn, dir and info. Only applies to the current document.

var loug = require('loug');

loug.set(true);

LICENCE

MIT