How to stop verbose output to the console about lite-server

[houbenbert]

If you do not want to see all HTTP requests, you will need to disable the logging middleware as described in README.md.

So in stead of a bs-config.json , use a bs-config.js file like this one:

module.exports = {
  logLevel: "silent",
  server: {
    middleware: {
      0: null
    }
  }
};

the 0:null clears out the first middleware, which is the logger.
You might still want to set the logLevel to "silent" or "debug" as well, since browsersync by itself can be quite verbose as well

[GabrielDelepine]

Personally I wanted to keep the middleware logger, but hide the success response. So I finally use npm start |grep -v "200" |grep -v "304"

[raphaelparent]

👍 would love to have a way to hide those logs.

[terciodemelo]

I'd recommend to write your "lite" script like that:
"lite": "lite-server -c bs-config.json > /dev/null",
It works fine to me

[lasanthabandara]

Thanks @houbenbert ! works like a charm!

[rbosneag]

Thanks @GabrielDelepine, exactly what I needed!

[fromcouch]

Any change to remove 200 and 304 code natively?

I have the same behaviour and I wish to made via bs-config.

Thanks

[hamioraz]

A quick hack: lite-server configures the http request logger in lib\config-defaults.js which in turn uses the module 'connect-logger'

var log = require('connect-logger')

Intercept log messages by putting a wrapper around the log function:

var proxy = function(options) {

    console.log('Proxy logger');
    var targetLog = log(options);

    return function(req, res, next) {
        var originalEnd = res.end;
        var targetNext = targetLog(req, res, next);

        //res.end is now a new function
        var targetEnd = res.end;

        res.end = function(chunk, encoding) {
            if (res.statusCode === 200 || res.statusCode === 304) {
                res.end = originalEnd;
                res.end(chunk, encoding);
                return undefined;
            } else {
                return targetEnd(chunk, encoding);
            }
        };
        return targetNext;
    };
}

And in the middleware config replace log() with proxy():

proxy({ format: '%date %status %method %url' })

A bit painful because of the nesting hell. Probably a simpler solution but works for me