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

saneconsole

v0.1.4

Published

a little more than console.log()

Downloads

1

Readme

I don't remember publishing an npm package either.

builds a simple logging library as his first npm package

This is how saneconsole came to be.

Using it is simple.

First, you'll have to install the package.


npm install saneconsole

Then, here's how to use it in one of your files


var saneconsole = require('saneconsole');
var meta = { }
// Set meta to any Object or String you'd like to be logged everytime.
// It could be the user's id or the entire user object
var console = saneconsole(meta);

NOTE: Logging to the file does not work on the client as the fs module isn't avaible there.

In order to use it on the web client, you will have to pass another boolean param when initializing the package.

var console = saneconsole(meta);

will become

var console = saneconsole(meta, true);

And add the below object to your webpack config

node: {
  fs: "empty"
}

You can also declare it in the global scope, using global on Node and window.console on the client.

It also adds a time stamp, and a prefix to the log.


console.log("Hi! I'm Nishant")

would be printed as


DEBUG: [ 2017-07-28T19:20:39.733Z ] :  Hi! I'm Nishant

As of now saneconsole only supports console.log, console.warn, and console.error

No logs are printed on production. You can finally say goodbye to that no-console rule in your eslint config.

All logs are found in the saneconsole.log file in the root of your project. They are just a series of JSON objects. You could easily convert them into an array of JSON objects and make them searchable.

Here is the object that gets added to the file:


{"timestamp":"2017-07-28T19:50:53.223Z","info":["Hi! I'm Nishant"],"meta":"123"}

A dashboard to view and search these logs coming up after the next boring class I attend.