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

examplify-log

v1.3.2

Published

Just a very simple logging module for Examplify

Downloads

3

Readme

electron-log

Build Status npm version

Description

Just a very simple logging module for your Electron or NW.js application. No dependencies. No complicated configuration. Just require and use. Also it can be used without Electron.

By default it writes logs to the following locations:

  • on Linux: ~/.config/<app name>/log.log
  • on OS X: ~/Library/Logs/<app name>/log.log
  • on Windows: %USERPROFILE%\AppData\Roaming\<app name>\log.log

Installation

Install with npm:

npm install electron-log

Usage

var log = require('electron-log');

log.info('Hello, log');

Transport

Transport is a simple function which requires an object which describes a message. By default, two transports are active: console and file. The file path is dependent on current platform.

Disable default transport:

log.transports.file = false;
log.transports.console = false;

Override transport:

log.transports.console = function(msg) {
  console.log(`[${msg.date.toLocaleTimeString()} ${msg.level}] ${msg.text}`);
};

Console Transport

// Log level
log.transports.console.level = 'warn';

/** 
 * Set output format template. Available variables:
 * Main: {level}, {text}
 * Date: {y},{m},{d},{h},{i},{s},{ms}
 */
log.transports.console.format = '{h}:{i}:{s}:{ms} {text}';

// Set a function which formats output
log.transports.console.format = (msg) => msg.text;

File transport

// Same as for console transport
log.transports.file.level = 'warn';
log.transports.file.format = '{h}:{i}:{s}:{ms} {text}';

// Set maximum log size in bytes. When it exceeds, old log will be saved
// as log.old.log file
log.transports.file.maxSize = 5 * 1024 * 1024;

// Write to this file, must be set before first logging
log.transports.file.file = __dirname + '/log.txt';

// fs.createWriteStream options, must be set before first logging
log.transports.file.streamConfig = { flags: 'w' };

// set existed file stream
log.transports.file.stream = fs.createWriteStream('log.txt');

By default, file transport reads a productName or name property from package.json to determine a log path like ~/.config/<app name>/log.log. If you have no package.json or you want to specify another , just set the appName property:

log.appName = 'test';

Change Log

1.3.0

  • #18 Rename 'warning' log level to 'warn'

1.2.0

  • #14 Use native console levels instead of console.log

1.0.16

  • Prefer to use package.json:productName instead of package.json:name to determine a log path.

License

Licensed under MIT.