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

electron-log-unconfig

v0.0.5

Published

A very simple logging module for your Electron application with unconfig

Downloads

9

Readme

electron-log

NPM version

Declare

Forked from electron-log@4.4.8

changes in this fork

  • You can add a .logrc or .logrc.json file in the project root directory and configure the log output method.
  • You can add a .logrc field to package.json and configure the log output method.
  • If you don't add config file or field, it works as normal electron-log.

Usage

npm install electron-log-unconfig -D

And then you can add a config file named .logrc or .logrc.json to root or add a .logrc field to package.json.

Options

Both config file and field have samed options.

{
  "filePath": "D:/logs",
  "fileName": "Test-{y}-{m}-{d}",
  "maxSize": 100,
  "segmentation": true,
  "prefixPkgName": false,
  "countLength": 3
}

filePath

  • Required: false
  • Type: string

The log output path.

fileName

  • Required: false
  • Type: string

File name's template. It will replace with date.

For example(Today is 2024/2/1):

Test-{y}-{m}-{d}      ->  filename: Test-2024-2-1.log
Test-{y}-{m}          ->  filename: Test-2024-2.log
Test-{y}              ->  filename: Test-2024.log
Test-{y}-AA{m}-BB{d}  ->  filename: Test-2024-AA2-BB1.log

maxSize

  • Required: false
  • Type: number
  • Default: 1024

Single file's size. The unit ofmeasurement is magabytes.

segmentation

  • Required: false
  • Type: boolean
  • Default: false

Whether to enable file splitting.

prefixPkgName

  • Required: false
  • Type: boolean
  • Default: false

Whether to add package name as prefix.

countLength

  • Required: false
  • Type: number
  • Default: 3

Default filename(if segmentation is true) is xxx.001.log.

If set countLength to 5, filename is xxx.00001.log.

Future

Maybe i will rewrite electron-log.But for now i'm just going to add a few methods to meet my needs.