Skip to content

Releases: monksoftware/monlog

Version 4.1.1

14 May 11:24
c94ba69
Compare
Choose a tag to compare

Update dependencies to fix security vulnterabilities

Version 4.1.0

06 Jun 13:12
c992bd5
Compare
Choose a tag to compare
  • Update devDependencies to fix js-yaml security issues (bonus: number of dependencies and size is reduced)
  • Fix type declarations
  • Update loglevel version, new one comes with built-in typescript declaration; @types/loglevel is not needed anymore
  • Fix test that was broken by recent package name change

Version 4.0.0

06 Jun 13:18
4a8b562
Compare
Choose a tag to compare

Changed package name from monk-log to monlog! Now part of the "mon" ecosystem, together with monredis and, soon, other useful packages.

The package is now published on NPM in the @monksoftware namespace: @monksoftware/monlog

Version 3.2.0

27 Mar 23:09
Compare
Choose a tag to compare

Improved type declarations.

Previously, we just reexported the loglevel types. Now, we augmented those by adding the type signatures of all our additional stuff.

Version 3.1.0

24 Mar 00:57
Compare
Choose a tag to compare

Add typescript type declarations

Version 3.0.1

05 Mar 15:59
Compare
Choose a tag to compare

Fix critical bug in package.json that made the library not install correctly using npm/yarn

Version 3.0.0

04 Mar 10:17
Compare
Choose a tag to compare
  • Changed the default log format. Now the timestamp is printed in the current timezone instead of UTC, and the timezone is printed. Example: 2019-03-04T11:13:00.432 becomes (if running the script in a GMT +1 timezone): 2019-03-04T12:13:00.432+01:00. The new format follows RFC3339
  • Some initial unit tests
  • Upload only necessary stuff to NPM when publishing

Version 2.2.0

22 Feb 12:15
Compare
Choose a tag to compare

Use Object.assign instead of the object spread operator syntax in order to support older versions of node (< 8.15).

Version 2.1.0

18 Feb 11:30
Compare
Choose a tag to compare

Now child loggers correctly inherit parent level; instead of always defaulting to WARN.
For example you can now use setDefaultLevel in the entrypoint of your app to make all loggers created after that use that log level.

Version 2.0.0

18 Feb 09:49
1e12f6e
Compare
Choose a tag to compare
v2.0.0

Merge pull request #1 from monksoftware/logger-default-export-and-ref…