This package has been deprecated

Author message:

This package is no longer maintained. If you would like to use the functionality offered by this package, please consider publishing a fork of this package under your own npm scope.

winston-gulplog

DEPRECATED: This package is no longer maintained. If you can justify my continued support of this package, please file an issue. If you would like to take over maintainership of this package on the Npm registry, please open an issue.

A transport for winston that sends log messages to gulplog.

winston-gulplog is a transport for the winston logger. winston-gulplog submits log events to gulplog, a singleton logger used by the gulp task runner.

Table of Contents

• Installation
• Usage
• Node Support Policy
• Contributing

Installation

To install winston-gulplog for use in your project please run the following command:

yarn add [--dev] winston-gulplog

Usage

If you already have a winston logger instance, called logger, you can add the winston-gulplog transport like so:

const Gulplog = require(`winston-gulplog`);
 
logger.add(Gulplog);

It can also be added at the time a new winston logger is instantiated:

const Gulplog = require(`winston-gulplog`);
 
const logger = new winston.Logger({
  transports: [
    new Gulplog()
  ]
});

Now, when logging to your winston instance, any message sent to a log level will be sent to the same log level for gulplog. Please keep in mind that any metadata sent to your winston instance will not be sent to gulplog.

Node Support Policy

We only support Long-Term Support versions of Node.

We specifically limit our support to LTS versions of Node, not because this package won't work on other versions, but because we have a limited amount of time, and supporting LTS offers the greatest return on that investment.

It's possible this package will work correctly on newer versions of Node. It may even be possible to use this package on older versions of Node, though that's more unlikely as we'll make every effort to take advantage of features available in the oldest LTS version we support.

As each Node LTS version reaches its end-of-life we will remove that version from the node engines property of our package's package.json file. Removing a Node version is considered a breaking change and will entail the publishing of a new major version of this package. We will not accept any requests to support an end-of-life version of Node. Any merge requests or issues supporting an end-of-life version of Node will be closed.

We will accept code that allows this package to run on newer, non-LTS, versions of Node. Furthermore, we will attempt to ensure our own changes work on the latest version of Node. To help in that commitment, our continuous integration setup runs against all LTS versions of Node in addition the most recent Node release; called current.

JavaScript package managers should allow you to install this package with any version of Node, with, at most, a warning if your version of Node does not fall within the range specified by our node engines property. If you encounter issues installing this package, please report the issue to your package manager.

Contributing

Please read our contributing guide on how you can help improve this project.