
Security News
The Changelog Podcast: Practical Steps to Stay Safe on npm
Learn the essential steps every developer should take to stay secure on npm and reduce exposure to supply chain attacks.
Easy to use (config-based) wrapper around winston logger
7 -> debug6 -> info5 -> notice4 -> warning3 -> error2 -> crit1 -> alert0 -> emergnpm i @c8/logger
// import logger component
var logger = require('logger')
// Define config options
var config = {
  transports: {
    console: {
      level: ['info', 'debug'],
      options: {}
    },
    file: {
      level: ['error', 'crit', 'alert', 'emerg'],
      options: {}
    }
  }
}
// Initialize Logger config
logger.init(config)
// Use logger
logger.debug('This is the debug message')
Console logger options: console.options
File logger options: file.options
In order to use the logger as an Express middleware you should add:
var loggerMiddleware = logger.middleware.Express
server.use(loggerMiddleware.debug)
// or
 
server.get('/', loggerMiddleware.debug, function (req, res) {
  res.status(200)
}
The middleware logger uses the same config you pass in logger.init(/*config*/) and depending on the log level method you use the middleware with it will be sent to the transport specified in the config.
The middleware can be used globally before any route server.use(loggerMiddleware.debug) or route specific server.get('/route', loggerMiddleware.debug, function (req, res) {...})
All error logs are pushed using levels error, crit, alert, emerg and should be defined under the route declaration:
// ^^^ all routes are defined above ^^^
// use 'error' method for error printing
server.use(loggerMiddleware.error)
Logger has a default log messages formatting. There are 2 different use-cases on how the formatting will look like:
logger.debug('log message'){{timestamp}} {{hostname}} {{logLevel}} {{logMessage}}logger.debug('log message', new Error('My Log Error')){{timestamp}} {{hostname}} {{errorType}}:{{errorMessage}} {{path:line:column}} {{logLevel}} {{logMessage}}Run the following commands:
npm run test for unit testsnpm run standard for StandardJS compilingnpm run coverage for code coverageMIT Licence © Copyright 2016 C8 MANAGEMENT LIMITED
FAQs
Easy to use (config-based) wrapper around winston logger
We found that @c8/logger demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 5 open source maintainers collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Security News
Learn the essential steps every developer should take to stay secure on npm and reduce exposure to supply chain attacks.

Security News
Experts push back on new claims about AI-driven ransomware, warning that hype and sponsored research are distorting how the threat is understood.

Security News
Ruby's creator Matz assumes control of RubyGems and Bundler repositories while former maintainers agree to step back and transfer all rights to end the dispute.