@imqueue/async-logger 2.0.0 → 2.0.1

package/README.md

@@ -14,20 +14,20 @@ There are two actual ways of using async logger.
 
 1. Rely on singleton instance produced by this library, which is configured by
    environment variables (see Configuration section below)
-   
+
    In this case as simple as
    ~~~typescript
-   import logger from '@imqueue/async-async-logger';
-   
+   import logger from '@imqueue/async-logger';
+
    serviceOptions.logger = logger;
    ~~~
 
 2. Instantiate and configure async logger programmatically:
    ~~~typescript
-   import { Logger } from '@imqueue/async-async-logger';
-   
+   import { Logger } from '@imqueue/async-logger';
+
    const { name, version } = require('./package.json');
-   
+
    const logger = new Logger({
        transports: [{
            type: 'http',
@@ -48,7 +48,7 @@ There are two actual ways of using async logger.
            hostname: 'localhost'
        },
    });
-   
+
    serviceOptions.logger = logger;
    ~~~
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@imqueue/async-logger",
-  "version": "2.0.0",
+  "version": "2.0.1",
   "description": "Configurable async logger over winston for @imqueue services",
   "keywords": [
     "logger",

package/src/Logger.js

@@ -109,8 +109,8 @@ exports.Logger = Logger;
  */
 Logger.console = {
     log: (...args) => setTimeout(() => console.log(...args)),
-    info: (...args) => setTimeout(() => console.log(...args)),
-    warn: (...args) => setTimeout(() => console.log(...args)),
-    error: (...args) => setTimeout(() => console.log(...args)),
+    info: (...args) => setTimeout(() => console.info(...args)),
+    warn: (...args) => setTimeout(() => console.warn(...args)),
+    error: (...args) => setTimeout(() => console.error(...args)),
 };
 //# sourceMappingURL=Logger.js.map