Skip to content

Releases: jamonkko/console-log-server

v0.4.0

30 Oct 21:12
Compare
Choose a tag to compare

What's Changed

  • New cli flags (mostly needed for testing, but can be useful e.g. if using console-log-server in scripts). See details of the flags from README.md.
    • --silent-start
    • --mock-date
    • --indent-response
    • --sort-fields
  • Added automatic compatibility tests with older node versions.
  • Support to increase the raw body limit that bodyParser can handle by @jamonkko in #6
    • --raw-body-limit
  • Fix number as body by @jamonkko in #9

Full Changelog: v0.3.0...v0.4.0

0.3.0

03 Jun 11:25
Compare
Choose a tag to compare

New features and improvements

  • Proxy support
  • Logging of response
  • Support all node >= 0.10 versions
  • Support listening of multiple hosts
  • Fix pretty printing of multiline string value inside json
  • Request id (counter + client defined id) printed in divider
  • Updated Babel to v7
  • Changed to use prettier-standard
  • Removed internal meta part, instead print date as part of divider
  • Some dependency update
  • Fix compatibility problem with old node versions #3
  • --default-cors=no cli arg can be used to turn injecting cors on/off

Breaking changes

  • Custom logger opts.log function changed to opts.console (to support grouping/indenting in newer node versions)
  • result cli flags are renamed to response to be more consistent with request/response terminology. E.g. instead of --result-body flag you need to use --response-body. Same applies to opts.resultCode -> opts.responseCode.

0.2.1

15 Nov 20:20
Compare
Choose a tag to compare
  • Updated readme

v0.2.0

15 Nov 16:39
Compare
Choose a tag to compare
  • Added CORS headers (thanks @avantassel) #4
  • Datetime when request is received is logged under meta-section. By default printing local time + offset since that might be most human readable for most use cases but you can customise the format with cli flags or using the opts if using programmatically.