winston-elasticsearch: Logger transports for elastic gets deleted when there is an error writing the logs to Elasticsearch

When there is an error writing logs to the elasticsearch (for example writing different types for a field), the error subscription is invoked the first time successfully. However on subsequent errors, the logger fails with the error “[winston ]Attempt to write logs with no transports” The reason is because the elastic transport in the logger gets deleted after the exception.

var logger = winston.createLogger({
  transports: [
    new Elasticsearch(esTransportOpts)
  ],
  exitOnError: false
});

logger .on('error', (err) => {
    // elastic transport is deleted in logger object
    console.log('error writing to elasticsearch');
});

Expected Results: The transport should not be deleted after the exception.