chore(deps): Update dependencies and drop node < 10 support

Author: leguellec

.commitlintrc.yml

@@ -1,12 +1,12 @@
 rules:
-  type-enum:
-    - 2
-    - always
-    - ["feat", "fix", "docs", "style", "refactor", "perf", "test", "build", "ci", "chore", "revert"]
-  subject-empty:
-    - 2
-    - never
-  subject-max-length:
-    - 2
-    - always
-    - 80
+    type-enum:
+        - 2
+        - always
+        - ['feat', 'fix', 'docs', 'style', 'refactor', 'perf', 'test', 'build', 'ci', 'chore', 'revert']
+    subject-empty:
+        - 2
+        - never
+    subject-max-length:
+        - 2
+        - always
+        - 80

.eslintrc.yml

@@ -1,9 +1,9 @@
 parserOptions:
-  ecmaVersion: 9
-  sourceType: script
+    ecmaVersion: 9
+    sourceType: script
 env:
-  node: true
-  es6: true
+    node: true
+    es6: true
 extends: eslint:recommended
 rules:
-  no-unused-vars: off
+    no-unused-vars: off

.travis.yml

@@ -1,16 +1,15 @@
 language: node_js
 node_js:
-- '8'
-- '10'
-- '12'
-- '13'
+    - '10'
+    - '12'
+    - '13'
 script:
-- yarn run lint
-- yarn run check-fmt
-- yarn run tsc
-- yarn run test-cover
+    - yarn run lint
+    - yarn run check-fmt
+    - yarn run tsc
+    - yarn run test-cover
 after_success:
-- yarn run coverage
+    - yarn run coverage
 notifications:
-  slack:
-    secure: vuBp7KKQqHax5B/9NS7D8GiedcpLPXrfe7gzsyDow89rcqv6O6dtePzF1QtujsCVExRYNhApgCSb+cA30aHaJih6sQ9F3/suPSa1ql1AbpNmpxuQFFGO2LiRIHQ5cFMiBpvr4vP/nK3emwdRukKNmVgVcikYUCmJhrEXaL2YvCWq2amZj8pe/r2PCaeHknG2hVsJGhEHIxAwGqBtQQGI+z65MWebSAdLnmdPAoGDYfHRMKyhkFrF0BDsrCFOWRp/AoZ4rr6oqTZ7h97wTRKTNXoVcBoFp2dvXOuA3xuWrQvGFAIWdgkUwRHrN0ALuGy6/vZLhGldcKgvhQtEXCXeBCb/JQ15MjaUaxtcpUxkcZ/kHObqe1XXdbZbhGImkdg4ea7IH4H0pCzRyGieBbH63Mb0Pu46UCqAmCjjeKYPsSa3dOPXBHc48AP/zS1QrBxYeH7GwHmQZN4L39g2POWLu5Td0FfIIiDB/Y9ryE87mRkLFE0IGpFT+DlWGII1L75kgs673DFwbyuOGSoBUKdEV6TcGEmE4ExitBQwjwfDiZLY1ouL1WlTbcj84X9ou4idlCxBGScaaR/E4ddwEMH8C8C/QMRlpDQLyRJYH6PP1S7T8XCr7LHvLxaMn0C8TcRaXo0m8UdSy3kcWvAUCvgVXAngTZE1fzRELN4IaELwwfY=
+    slack:
+        secure: vuBp7KKQqHax5B/9NS7D8GiedcpLPXrfe7gzsyDow89rcqv6O6dtePzF1QtujsCVExRYNhApgCSb+cA30aHaJih6sQ9F3/suPSa1ql1AbpNmpxuQFFGO2LiRIHQ5cFMiBpvr4vP/nK3emwdRukKNmVgVcikYUCmJhrEXaL2YvCWq2amZj8pe/r2PCaeHknG2hVsJGhEHIxAwGqBtQQGI+z65MWebSAdLnmdPAoGDYfHRMKyhkFrF0BDsrCFOWRp/AoZ4rr6oqTZ7h97wTRKTNXoVcBoFp2dvXOuA3xuWrQvGFAIWdgkUwRHrN0ALuGy6/vZLhGldcKgvhQtEXCXeBCb/JQ15MjaUaxtcpUxkcZ/kHObqe1XXdbZbhGImkdg4ea7IH4H0pCzRyGieBbH63Mb0Pu46UCqAmCjjeKYPsSa3dOPXBHc48AP/zS1QrBxYeH7GwHmQZN4L39g2POWLu5Td0FfIIiDB/Y9ryE87mRkLFE0IGpFT+DlWGII1L75kgs673DFwbyuOGSoBUKdEV6TcGEmE4ExitBQwjwfDiZLY1ouL1WlTbcj84X9ou4idlCxBGScaaR/E4ddwEMH8C8C/QMRlpDQLyRJYH6PP1S7T8XCr7LHvLxaMn0C8TcRaXo0m8UdSy3kcWvAUCvgVXAngTZE1fzRELN4IaELwwfY=

README.md

@@ -7,25 +7,25 @@
 
 A Lightweight logger that combines debug namespacing capabilities with winston levels and multioutput
 
-- [Installation](#installation)
-- [Usage](#usage)
-    - [Using context ID](#using-context-id)
-    - [Using namespaces](#using-namespaces)
-    - [Outputs](#outputs)
-    - [Metadata](#metadata)
-- [TypeScript](#typescript)
+-   [Installation](#installation)
+-   [Usage](#usage)
+    -   [Using context ID](#using-context-id)
+    -   [Using namespaces](#using-namespaces)
+    -   [Outputs](#outputs)
+    -   [Metadata](#metadata)
+-   [TypeScript](#typescript)
 
 ## Installation
 
 Using npm:
 
-``` sh
+```sh
 npm install @ekino/logger
 ```
 
 Or yarn:
 
-``` sh
+```sh
 yarn add @ekino/logger
 ```
 
@@ -40,12 +40,12 @@ A log instance is bounded to a namespace. To use it, instantiate a logger with a
 
 This logger define 5 log levels: error, warn, info, debug, trace.
 When you set a level, all levels above it are enabled too.
-Log level can be set by calling `setLevel` function. 
+Log level can be set by calling `setLevel` function.
 
 For example, enabling `info` will enable `info`, `warn` and `error` but not `debug` or `trace`.
 The "special" log level `none` means no log and can only be used to set a namespace level.
 
-``` js
+```js
 { trace: 0, debug: 1, info: 2, warn: 3, error: 4 }
 ```
 
@@ -69,7 +69,7 @@ logger.debug('sample message', {
 })
 ```
 
-output: 
+output:
 
 ![Example](docs/images/example_usage1.gif)
 
@@ -79,15 +79,15 @@ One of the main complexity working with node is ability to follow all logs attac
 This is not mandatory, but based on our experience, we recommend as a best practice to add a unique identifier that will be passed all along functions calls.
 When you log something, you can provide this id as a first parameter and logger will log it. If not provided, it's auto generated.
 
-The signature of the function with contextId is: 
+The signature of the function with contextId is:
 
 ```js
 my_log.the_level(contextId, message, data)
 ```
 
 Example app.js
 
-``` javascript
+```javascript
 const { setNamespaces, setLevel, createLogger } = require('@ekino/logger')
 
 setNamespaces('root:*')
@@ -99,25 +99,25 @@ logger.debug('ctxId', 'log with predefined context ID', {
 })
 ```
 
-output: 
+output:
 
 ![Example](docs/images/example_usage2.gif)
 
 ### Using namespaces
 
 Logger relies on namespaces. When you want to log something, you should define a namespace that is bound to it.
 When you debug, this gives you the flexibility to enable only the namespaces you need to output.
-As a good practice, we recommend setting a namespace by folder / file. 
+As a good practice, we recommend setting a namespace by folder / file.
 For example for a file in modules/login/dao you could define 'modules:login:dao'.
 Warning, "=" can't be part of the namespace as it's a reserved symbol.
 
 You can also define a level per namespace. If no level is defined, the default global level is used.
 To disable logs of a namespace, you can specify a level `none`
-A namespace ':*' means eveything after ':' will be enabled. Namespaces are parsed as regexp.
+A namespace ':\*' means eveything after ':' will be enabled. Namespaces are parsed as regexp.
 
-To define namespace level, you should suffix namespace with "=the_level" 
-For example let's say you need to enable all info logs but for debug purpose you need to lower the level 
-of the namespace database to `debug`. You could then use: 
+To define namespace level, you should suffix namespace with "=the_level"
+For example let's say you need to enable all info logs but for debug purpose you need to lower the level
+of the namespace database to `debug`. You could then use:
 
 ```js
 const { setLevel, setNamespaces } = require('@ekino/logger')
@@ -173,11 +173,11 @@ setOutput(outputs.json)
 const logger = createLogger('namespace:subNamespace')
 logger.debug('ctxId', 'Will be logged', {
     someData: 'someValue',
-    someData2: 'someValue'
+    someData2: 'someValue',
 })
 ```
 
-output: 
+output:
 
 ![Example](docs/images/example_usage3.gif)
 
@@ -187,27 +187,27 @@ Pretty will output a yaml like content.
 
 ```js
 const { setNamespaces, setLevel, setOutput, outputs, createLogger } = require('@ekino/logger')
-    
+
 setNamespaces('namespace:*')
 setLevel('debug')
 setOutput(outputs.pretty)
 
 const logger = createLogger('namespace:subNamespace')
 logger.debug('ctxId', 'Will be logged', {
     someData: 'someValue',
-    someData2: 'someValue'
+    someData2: 'someValue',
 })
 ```
 
-output: 
+output:
 
 ![Example](docs/images/example_pretty.gif)
 
 #### Output function
 
 An output, is a function that will receive log data and should transform and store it
 
-Log data follow the format: 
+Log data follow the format:
 
 ```
 {
@@ -223,22 +223,22 @@ Log data follow the format:
 
 ```js
 const { setNamespaces, setLevel, setOutput, outputs, outputUtils, createLogger } = require('@ekino/logger')
-    
+
 setNamespaces('namespace:*')
 setLevel('debug')
 
 const consoleAdapter = (log) => {
     console.log(outputUtils.stringify(log))
 }
 
-// This will output in stdout with the pretty output 
+// This will output in stdout with the pretty output
 // and in the same will log through native console.log() function (usually to stdout too)
 setOutput([outputs.pretty, consoleAdapter])
 
 const logger = createLogger('namespace:subNamespace')
 logger.debug('ctxId', 'Will be logged', {
     someData: 'someValue',
-    someData2: 'someValue'
+    someData2: 'someValue',
 })
 ```
 
@@ -258,12 +258,12 @@ const consoleAdapter = (log) => {
 ### Log data
 
 Most of the time, a log message is not enough to guess context.
-You can append arbitrary data to your logs. 
+You can append arbitrary data to your logs.
 If you're using some kind of log collector, you'll then be able to extract those values and inject them in elasticsearch for example.
 
 ```js
 const { setOutput, setNamespaces, setLevel, createLogger } = require('@ekino/logger')
-    
+
 setOutput('pretty')
 setNamespaces('namespace:*')
 setLevel('info')
@@ -272,7 +272,7 @@ const logger = createLogger('namespace:subNamespace')
 logger.warn('message', { someData: 'someValue' })
 ```
 
-output: 
+output:
 
 ![Example](docs/images/example_data.gif)
 
@@ -293,7 +293,7 @@ const logger = createLogger('namespace')
 logger.warn('message', { someData: 'someValue' })
 ```
 
-output: 
+output:
 
 ![Example](docs/images/example_context.gif)