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 🙏

© 2026 – Pkg Stats / Ryan Hefner

winston-appenlight

v0.1.1

Published

AppEnlight transport for Winston

Readme

winston-appenlight

AppEnlight Transport for Winston

Usage

Just like with any other Winston transport, this can be set up by passing it as a new "transport":

var AppEnlight = require('winston-appenlight');

var logger = new winston.Logger({
	transports: [
		new AppEnlight({
			level: 'info',
			namespace: 'MY_APP_NAMESPACE',
			key: 'MY_AE_KEY',
			base_url: 'OPTIONAL_AE_CUSTOM_URL', // Default https://api.appenlight.com/api
			// Optional global tags to send along with every request
			tags: {
				app: 'OptionalAppName',
				node_env: process.env.NODE_ENV,
				// extra tags here
			},
		}),
	],
});

However, if used in conjunction with express-appenlight you'll want to pass in the agent from express-appenlight as the second argument:

var logger = new winston.Logger({
	transports: [
		new AppEnlight(APPENLIGHT_CONFIG, require('express-appenlight').agent),
	],
});

This adds the request_id that's used in express-appenlight along with all log requests. If you have your own req.id already set, both express-appenlight and winston-appenlight will use that ID instead of generating a new one.

This can be very useful if you want to tie front-end logging with back-end logging:

// Adds a request ID which will be used for winston
// on the back-end, and allow us to use that same
// request ID on any front-end logging
app.use(function(req, res, next){
	req.id = uuid.v4();
	res.setHeader('X-Request-ID', req.id);
	next();
});