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

winston-endpoint

v1.0.1

Published

Winston transport for sending logs to an HTTP endpoint

Downloads

1,808

Readme

npm version Build status Dependencies

Motivation

The HTTP transport included with winston uses a JSON-RPC format, which is not how all log services expect their data. This transport allows a more customizable format.

Use

Each of the following methods will add this transport to your instance of winston. You may try any of these examples by first creating a RequestBin at https://requestb.in/ and using it in place of the URL below. See the fourth example for an overview of available options.

const winston = require('winston');
const Endpoint = require('winston-endpoint');
winston.add(Endpoint, { url: 'http://requestb.in/1hc2i4h13' });
winston.info('So say we all.');
const winston = require('winston');
const Endpoint = require('winston-endpoint');
winston.configure({
  transports: [
    new Endpoint({ url: 'http://requestb.in/1hc2i4h13' })
  ]
});
winston.info('So say we all.');
const winston = require('winston');
const Endpoint = require('winston-endpoint');
const logger = new winston.Logger({
  transports: [
    new Endpoint({ url: 'http://requestb.in/1hc2i4h13' })
  ]
})
logger.info('So say we all.');
const winston = require('winston');
const Endpoint = require('winston-endpoint');
winston.loggers.add('galactica', {
  endpoint: {
    url: 'http://requestb.in/1hc2i4h13', // endpoint to send logs to (no default)
    json: false, // send the log as a JSON object or a plain string (default: false)
    silent: false, // setting to true will effectively turn this transport off (default: false)
    level: 'info', // the minimum level required to trigger this transport
    prependLevel: true, // when json: false, whether to add the log level to the beginning of the string (default: true)
    appendMeta: true, // when json: false, whether to add the meta data object to the end of the string (default: true)
    http: {} // see below
  }
});
winston.loggers.get('galactica').info('So say we all.');

The underlying library for this transport is got, and you can pass any options it accepts through the http field in the options object.

🙃