Skip to content

Releases: Download/picolog

v1.0.4

Choose a tag to compare

@Download Download released this 14 Mar 01:19
  • Use string.split i.s.o regex for passing url parameters.
    Fixes #1 Parsing parameters in the URL can go into a loop and cause the page to hang
  • Removed doc generation from grunt tasks
  • Removed auto-generated docs (they were useless anyway)
  • Removed dependency on grunt-jsdoc
  • all-in-all, the repo is much smaller now

v1.0.3

Choose a tag to compare

@Download Download released this 16 Feb 22:08
1.0.3

v1.0.2

Choose a tag to compare

@Download Download released this 16 Feb 21:05
1.0.2

v1.0.1

Choose a tag to compare

@Download Download released this 16 Feb 15:36
  • Fixed an issue with handling of level NONE;
  • methods dir, time and timeEnd bound to those of console if it exists
  • Allow Picolog log object to be used as a console replacement.
  • Improved documentation
  • Increased test coverage
  • Automated build testing with Travis CI

v1.0.0

Choose a tag to compare

@Download Download released this 24 Dec 00:04

Hooray! v1.0.0!

The API was changed. It now more closely resembles the native logging API so it can be used as a polyfill for the console object in environments that don't have it. The methods dir, time and timeEnd are just no-ops though. assert should work however and will log an error if the condition does not evaluate to true, unless the logging level was set to 0 (log.NONE), or we are running on Node JS and process.env.NODE_ENV is set to 'production'. I also increased the test coverage for Node JS.

Stable
I truly feel this API should be stable now. I have been using this myself for a couple of months now and the changes that are implemented between 0.7.0 and 1.0.0 where all the result of me still missing something when using Picolog from day to day:

  • Ability to easily use the log object as a polyfill for Nashorn
  • Log level checks were not intuitive, so I reversed the order of the levels
  • Ability to easily set the log level when using from Node JS (browser was already ok)

Still missing:
I would love to be able to tie the Picolog log object to a java.util.Logger or org.log4j.Logger instance and have the script logging be added to my regular server log file. However, I think I will implement this by making a more generic NashornLoggingAdapter that implements the console object and feeds the log messages to a Logger instance on the Java side. So most likely, Picolog will not have to be changed for that.

Please give this microscopically smal logging library a spin and let me know what you think.

v0.7.0

v0.7.0 Pre-release
Pre-release

Choose a tag to compare

@Download Download released this 18 Nov 17:28
0.7.0: Added support for Nashorn.

v0.6.0

v0.6.0 Pre-release
Pre-release

Choose a tag to compare

@Download Download released this 01 Nov 14:46
0.6.0

v0.5.0

v0.5.0 Pre-release
Pre-release

Choose a tag to compare

@Download Download released this 01 Nov 01:35
0.5.0

v0.4.0

v0.4.0 Pre-release
Pre-release

Choose a tag to compare

@Download Download released this 12 Oct 14:55
0.4.0

v0.3.0

v0.3.0 Pre-release
Pre-release

Choose a tag to compare

@Download Download released this 12 Oct 13:48
0.3.0