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

lambda-le-logger

v0.2.1

Published

A way to send logs to the Logentries service, even from an AWS Lambda function.

Downloads

5

Readme

Lambda-Le-Logger

A way to send logs to the Logentries service, even from an AWS Lambda function.

Basic Usage

To use this, simply add the following to your code:

// Up with your other require statements, add this:
var logger = require('lambda-le-logger');

// ... and then down where your code actually starts doing things, add this:
logger.initLogger();

// After that, you can call the log/info/warn/error methods at any time:
logger.info('Starting...');

Make sure you call initLogger() on each execution of your code, before you start sending logs to Logentries.

Methods

initLogger()

Initialize the (internal) logger instance. Call this before sending log data.

log(message) / info(message) / warn(message) / error(message)

Send log data to Logentries.

registerCompletionCallback(callback)

Register a function to be called ONCE as soon as the last of the currently-pending attempts at sending a log message has completed (successfully or not). If there are currently no pending messages, the callback will be called immediately. No parameters will be sent to the callback you provide.

This can be helpful to use just before calling the main callback function of your lambda code, to allow the sending of logs to Logentries to complete before your lambda function terminates. For example:

logFunctions.registerCompletionCallback(function() {
  mainCallback(null, results);
});

If you don't do this, some of your logs might not make it to Logentries (which is one of the main reasons I wrote this library).

License

This code is made available under the MIT license.