pino - npm Package Compare versions
Comparing version 2.4.0 to 2.4.1
| { | ||
| "name": "pino", | ||
| "version": "2.4.0", | ||
| "version": "2.4.1", | ||
| "description": "fast and simple logger", | ||
@@ -5,0 +5,0 @@ "main": "pino.js", |
@@ -387,3 +387,3 @@ # pino [](https://travis-ci.org/mcollina/pino) | ||
| Read only. Holds the current log format version (as output in the `v` property of each log record). | ||
| Read only. Holds the current log format version (as output in the `v` property of each log record). | ||
@@ -680,3 +680,3 @@ | ||
| cb() | ||
| } | ||
| }) | ||
@@ -694,2 +694,22 @@ pump(process.stdin, split2(JSON.parse), myTransport) | ||
| <a name="pino-socket"></a> | ||
| ### pino-socket | ||
| [pino-socket][pino-socket] is a transport that will forward logs to a IPv4 | ||
| UDP or TCP socket. As an example, use `socat` to fake a listener: | ||
| ```sh | ||
| $ socat -v udp4-recvfrom:6000,fork exec:'/bin/cat' | ||
| ``` | ||
| And then run an application that uses `pino` for logging: | ||
| ```sh | ||
| $ node yourapp.js | pino-socket -p 6000 | ||
| ``` | ||
| You should see the logs from your application on both consoles. | ||
| [pino-socket]: https://www.npmjs.com/package/pino-socket | ||
| <a name="caveats"></a> | ||
@@ -696,0 +716,0 @@ ## Caveats |
New alerts
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
Fixed alerts
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
Improved metrics
- Total package byte prevSize
- increased by0.1%
470797
- Number of lines in readme file
- increased by2.6%
789
No dependency changes