CONTRIBUTING.md

CONTRIBUTING

TL;DR? The winston project recently shipped 3.0.0 out of RC and is actively working towards the next feature release as it continues to triage issues.

• Be kind & actively empathetic to one another
• What makes up [email protected]?
• What about [email protected]?!
• Could this be implemented as a format?
• Roadmap
  • Version 3.1.0

Looking for somewhere to help? Checkout the Roadmap & help triage open issues! Find an issue that looks like a duplicate? It probably is! Comment on it so we know it's maybe a duplicate 🙏.

What makes up [email protected]?

As of [email protected] the project has been broken out into a few modules:

• winston-transport: Transport stream implementation & legacy Transport wrapper.
• logform: All formats exports through winston.format
• LEVEL and MESSAGE symbols exposed through triple-beam.
• Shared test suite for community transports

Let's dig in deeper. The example below has been annotated to demonstrate the different packages that compose the example itself:

const { createLogger, transports, format } = require('winston');
const Transport = require('winston-transport');
const logform = require('logform');
const { combine, timestamp, label, printf } = logform.format;

// winston.format is require('logform')
console.log(logform.format === format) // true

const logger = createLogger({
  format: combine(
    label({ label: 'right meow!' }),
    timestamp(),
    printf(nfo => {
      return `${nfo.timestamp} [${nfo.label}] ${nfo.level}: ${nfo.message}`;
    })
  ),
  transports: [new transports.Console()]
});

What about [email protected]?!

If you are opening an issue regarding the 2.x release-line please know that 2.x work has ceased. The winston team will review PRs that fix issues, but as issues are opened we will close them.

You will commonly see this closing [email protected] issues:

Development `[email protected]` has ceased. Please consider upgrading to
`[email protected]`. If you feel strongly about this bug please open a PR against
the `2.x` branch. Thank you for using `winston`!

Could this be implemented as a format?

Before opening issues for new features consider if this feature could be implemented as a custom format. If it is, you will see your issue closed with this message:

This can be accomplished with using [custom formats](https://github.com/winstonjs/winston#creating-custom-formats) in `[email protected]`. Please consider upgrading.

Roadmap

Below is the list of items that make up the roadmap through 3.3.0. We are actively triaging the open issues, so it is likely a few more critical path items will be added to this list before the next release goes out.

• Version 3.1.0
• Version 3.2.0
• Version 3.3.0

Legend

• Unstarted work.
• Finished work.
• [-] Partially finished or in-progress work.

Version 3.1.0

High priority issues (non-blocking)

• Browser support
  • Unit tests for webpack & rollup
• Benchmarking for File and Stream transports:
  • Benchmarking integration in pino.
  • Upgrade pino to latest winston.
  • See: https://github.com/winstonjs/logmark
  • See also: pinojs/pino#232
• Move logged event into winston-transport to remove need for it in each individual Transport written or remove the logged event entirely.

Increased code & scenario coverage

• [-] Replace all vows-based tests.
  • [-] test/transports/*-test.js
• Code coverage tests above 80% for winston (currently ~72%).
  • [-] Core scenarios covered in abstract-winston-transport.

Communications / Compatibility

• README.md for winston-compat.
• All formats documented in logform.
• All existing transports documented in docs/transports.md.

Version 3.2.0

Querying, Streaming, Uncaught Exceptions

• [-] Streaming

Communications / Compatibility

• winstonjs.org documentation site.

Version 3.3.0

Querying, Streaming, Uncaught Exceptions

• [-] Querying