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

tcv_logger

v1.0.3

Published

Little package that generates log in .json file. Also generates lots of additional information about system environments

Downloads

10

Readme

Log library that I made to use whenever I was too lazy to 'console.log' everything. Generate a .json instead with a little more information about users environment.

First of all you have to manually set the locations of the logs using 'setPath':

yarn add tcv_logger
import Logger from 'tcv_logger';
import Path from 'path';

const path = Path.resolve(__dirname, 'logs');
Logger.setPath(path);

This will set ~/src/logs your default logging storage.

Then, all you have to do is use info or error to generate .json logs

import Logger from 'tcv_logger';

async function Foobar(){
  
  try {
    const response = await api.get('https://foo/bar/json/')
    Logger.info({response})
  } catch (error) {
    Logger.error({error})
  }
}

Note that each method expects an object as a parameter. The output should look like that:

{
	"log_type": "ERROR",
	"cpu_arc": "x64",
	"platform": "linux - Linux",
	"hostname": "CBYK-83",
	"home_dir": "/home/user",
	"cpus": "false",
	"network_interfaces": "false",
	"timestamp": "2020-03-09 14:39:29",
	"data": [
		{
			"error": {
				"message": "connect EHOSTUNREACH ",
				"name": "Error",
				"stack": "Error: connect EHOSTUNREACH \n    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1137:16)",
				"config": {
					"url": "https://foo/bar/json/",
					"method": "get",
					"headers": {
						"Accept": "application/json, text/plain, */*",
						"User-Agent": "axios/0.19.2"
					},
					"transformRequest": [
						null
					],
					"transformResponse": [
						null
					],
					"timeout": 0,
					"xsrfCookieName": "XSRF-TOKEN",
					"xsrfHeaderName": "X-XSRF-TOKEN",
					"maxContentLength": -1
				},
				"code": "EHOSTUNREACH"
			}
		}
	]
}

By default, CPUs and NetworkInterfaces logs are set to false. To change that, simple do:

Logger.setCpuLogs(true);
Logger.setNetworkInterfacesLogs(true);