New Case Study:See how Anthropic automated 95% of dependency reviews with Socket.Learn More
Socket
Sign inDemoInstall
Socket

@vrbo/pino-rotating-file

Package Overview
Dependencies
Maintainers
9
Versions
14
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@vrbo/pino-rotating-file - npm Package Compare versions

Comparing version 3.0.0 to 4.0.0

29

CHANGELOG.md

@@ -0,1 +1,28 @@

### [4.0.0] Breaking change
- [Breaking] Drop support for node < 12.
- Update Github test workflow to only test againt node v 14.x
- Update dependencies, npm, and engines in package.json to support node version >= 14.
### [3.0.0](https://github.com/expediagroup/pino-rotating-file/compare/v2.0.2...v3.0.0) (2021-02-25)
- [Breaking] Enable raw output for file-rotation-only cases. ([#28](https://github.com/ExpediaGroup/pino-rotating-file/pull/28)) ([15a1e1b](https://github.com/ExpediaGroup/pino-rotating-file/commit/2dbf9f0847d1a14de876dec2d64d4a7e115a1e1b))
- Output is no longer run though `JSON.stringify` if the `isJson` option is `false`. This affects output in the following way:
Previously, when logging entries run through `pino-pretty`, the output is wrapped in double-quotes on each line:
```
"[2021-02-23 22:10:29.888 +0000] INFO (myLabel): my log {"
" req: {"
" url: '/'"
" }"
"[2021-02-23 22:10:29.999 +0000] ERROR (myLabel): TypeError: my error log"
" at line 42"
...
```
Which would then require additional configurations for Splunk indexers to correctly parse the log.
Preferably in this case, it would just log the output as-is, without calling `JSON.stringify()` on it, like it is now.
These changes wrap the call to the output stream in a similar check for `isJson === false` that is happening in other use-cases, so that the raw `data` value will get passed directly to the destination stream, rather than first calling `${JSON.stringify(data)}\n`.
## [2.0.2](https://github.com/expediagroup/pino-rotating-file/compare/v2.0.1...v2.0.2) (2020-08-19)

@@ -15,3 +42,3 @@

### 2.0.0(https://github.com/expediagroup/pino-rotating-file/compare/v1.1.1...v2.0.0) (2020-08-10)
### [2.0.0](https://github.com/expediagroup/pino-rotating-file/compare/v1.1.1...v2.0.0) (2020-08-10)

@@ -18,0 +45,0 @@ - [Breaking] Drop support for node < 12.

8

package.json
{
"name": "@vrbo/pino-rotating-file",
"version": "3.0.0",
"version": "4.0.0",
"description": "A hapi-pino log transport for splitting logs into separate, automatically rotating files.",

@@ -36,3 +36,3 @@ "main": "lib/index.js",

"engines": {
"node": ">=12.0.0",
"node": ">=14.0.0",
"npm": ">=6.0.0"

@@ -60,3 +60,3 @@ },

"rotating-file-stream": "^2.1.3",
"split2": "^3.1.0",
"split2": "^4.0.0",
"through2": "^4.0.0"

@@ -70,3 +70,3 @@ },

"nyc": "^15.0.0",
"sinon": "^9.0.0",
"sinon": "^11.0.0",
"standard": "^16.0.0",

@@ -73,0 +73,0 @@ "std-mocks": "^1.0.1",

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc