@vrbo/pino-rotating-file - npm Package Versions

4.3.2 (2023-02-16)

Bug Fixes

• Altering the order of semantic release config file to have it correct (#56) (d4baf4e)

4.3.1 (2023-01-09)

Bug Fixes

• bump json5 from 1.0.1 to 1.0.2 (#49) (90a6333)

4.3.0 (2022-12-07)

Features

• Upgrade to node v16 (#48) (95de84d)

4.2.0 (2022-12-06)

Features

• empty commit to trigger release pipeline (#47) (3c1b3af)

4.1.0 (2022-01-06)

Features

• semantic-release: modify the semantic release config (#42) (1658957)

[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 (2021-02-25)

• [Breaking] Enable raw output for file-rotation-only cases. (#28) (15a1e1b)
• 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.1 (2020-08-19)

Bug Fixes

• release workflow: Update release.yml (#23) (326635b)

2.0.0 (2020-08-10)

• [Breaking] Drop support for node < 12.
• Update Github test workflow to only test againt node v 12.x
• Update dependencies, npm, and engines in package.json to support node version >= 12.