unable to log nested objects as metadata

[jonlb]

I'm not really sure if this is even supposed to be possible but everytime I try to log an object with several layers of nesting it crashes node yet I can util.inspect it just fine.

Here's the object I'm trying to log:

{ project: { basedir: '/home/jon/gits/JxLib', default: 'deploy' },
  app: 
   { name: 'jxlib',
     path: '/jxlib',
     version: '3.0',
     home: '/home/jon/gits/JxLib',
     build: '/home/jon/gits/JxLib/build',
     dist: '/home/jon/gits/JxLib/dist',
     deploy: '/home/jon/gits/JxLib/www',
     docs: '/home/jon/gits/JxLib/www/reference',
     vendor: '/home/jon/gits/JxLib/vendor',
     utils: '/home/jon/gits/JxLib/utils' },
  dependencies: { NaturalDocs: '/home/jon/gits/JxLib/utilsNaturalDocs-1.4/NaturalDocs' },
  loader: 
   { base: { moveImages: false, rewriteImageUrl: false },
     repos: 
      { core: { paths: { js: '/home/jon/gits/JxLib/vendor/mootools-core/Source' } },
        more: { paths: { js: '/home/jon/gits/JxLib/vendor/mootools-more/Source' } },
        jxlib: 
         { paths: 
            { js: '/home/jon/gits/JxLib/build/Source',
              css: '/home/jon/gits/JxLib/build/themes/{theme}/css',
              cssalt: '/home/jon/gits/JxLib/build/themes/{theme}' } } } },
  tasks: [],
  filepath: '/home/jon/gits/JxLib/builder/config.js',
  targets: '/home/jon/gits/JxLib/builder/targets' }

I'm passing it to a logger instance using something like:

logger.debug("log message", obj);

where obj is the one noted above.

is this correct behaviour or is it actually a bug somewhere?

Thanks,
Jon Bomgardner

[indexzero]

This is a bug

[rgabo]

README.md (Logging with Metadata) states that the Console and File transports use util.inspect. which is not the actual case, but rather constructs a single-level deep querystring-like string:(https://github.com/indexzero/winston/blob/master/lib/winston/internal.js#L91)

would be great if internal.log wouldn't be so much internal but customizable (custom formatters?) e.g. output like [level] message would better suit us than level: message, but today we have to fork to achieve this.

still, great work @indexzero, indispensable module in the node community. thanks from @sspinc.

[indexzero]

@rgabo Agreed. Pull request for this feature would be accepted

[dominictarr]

I tried this and it worked, can you upgrade to latest?

[indexzero]

Yes. This is fixed in winston@0.4.0