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

windows-eventlog-edge

v1.0.2

Published

Module to write to a Windows Event Log (Requires .Net)

Downloads

4

Readme

windows-eventlog-edge

Node module for writing to the Windows EventLog. This module uses Edge.js and requires .Net

Some of the naming conventions are intentionally PascalCase to match up against the .Net conventions, when you create a logger, you'll get to more familiar javascript-style camelCase syntax.

NOTE: There is a binary npm module called windows-eventlog.

Installation

npm install --save windows-eventlog-edge

Usage

// Import the module
var EventLog = require('windows-eventlog-edge');

// Create a logger via the generator methods
var logger = EventLog.Application('my-application');
  /*
      WARINING: After a log call, 'my-application' will be 
      bound to the specified log ("Application" in the example).  
      All future log entries for 'my-application' will go to 
      that log regardless of the generator specified after.

      EventLog.Application
      EventLog.Security
      EventLog.Setup
      EventLog.System
  	  EventLog.ForwardedEvents
  */

//Use the logger
//  logger.TYPE(message, [params...], [callback])
logger.info('message');
logger.warn('message %s', new Date());
logger.error(new Error('this will serialize with name, message and stack'));
logger.success('message', function(err){
	if (err) console.error(err);
});
logger.failure('message');

When you pass an object as the message it is formatted with JSON.stringify(message, null, 4). Objects (Errors) will keep their name. message and stack properties.

When you pass other arguments, util.format will be used.

WARNING

The first time a log entry is called, it will register the EventLog source, which will bind your "my-application" to that log. Guture calls will go to that log regardless of which log you specify after.

Your best bet is to stick to the Application log.

NOTES

The above methods in the end are friendly wrappers for calling:

EventLog(options, callback)

options

  • log is the name of the eventlog you are writing to:
    • Application (default)
    • Security
    • Setup
    • System
    • Forwarded Events
  • type is the type of entry being made:
    • Error (1)
    • Warning (2)
    • Information (3) (default)
    • SuccessAudit (8)
    • FailureAudit (16)
  • source is the name of your application/service/module.
    • defaults to module.parent.filename
  • message is the message you want to log.