Wrapped errors wrongly apply formatting

[pi0]

Using using wrap* helpers, we implicitly assume first argument as consola logObj format which might end with formatting errors. (nuxt/nuxt#8741)

Reproduction

const consola = require('consola')

const error = new Error('boom')
const errorObj = {
  date: new Date().toISOString(),
  level: 'error',
  message: error.message,
  error: { stack: error.stack, message: error.message }
}

console.log(errorObj)
consola.wrapAll()
console.log(errorObj)

Workarounds

1. Use different field name than message, error
2. console.log(JSON.stringify(errorObj, null, 2))
3. console.log('', errorObj)
4. consola.restoreAll()

[gkatsanos]

unfortunately workarounds dont work for us as they don't generate valid JSON (at least Datadog doesnt see it as such).
The only thing that seems to work is restoreAll() ...

[gkatsanos]

can I over-write the built in reporters of nuxt core with a setting in the nuxt.config.js ?

[pi0]

@gkatsanos You can set consola reporters in body of nuxt.config file. (nuxt/nuxt#8507 (comment))

Also respectfully, please use channels like nuxt discord to get help for your solutions such as datadog integration. I would also be more than happy if can help there. Sending random questions in several repo/issues is wasting time.

[pi0]

Issue fixed in v2.15.1

@gkatsanos You can get update with yarn upgrade nuxt (or better recreating lock file)

[gkatsanos]

@pi0 I think I need to wait until its propagated to the main repo, right? https://github.com/nuxt/nuxt.js/releases

[pi0]

@gkatsanos nop npm magic! (nuxt has range dependency on consola like ^2.15.0) when lock file is created, it will fetch latest possible in range :)

[gkatsanos]

@pi0 would you be available on the Vue Discord ? ( console.error ( { .. } ) still generates invalid JSON)

[pi0]

@gkatsanos Sure pi0#6582

[gkatsanos]

console.error when wrapped still adds ERROR in front of the object returned. reproduction: https://repl.it/@gkatsans/Consola-2#index.js
I guess this may be intended, in which case what would be the workaround? (also messaged you in Discord)

[pi0]

It is intended indeed. Fancy reporter adds the badge. So you should either opt-out in nuxt or replace reporters

[gkatsanos]

Thanks. I can add a parser in Datadog that handles it but I guess going with the previous suggestion of

consola.setReporters([
  {
    log: (e) => {
      process.stdout.write(JSON.stringify(e))
    },
  },
])

in nuxt.config.js seems a more safe solution as I could also do further manipulation there centrally.. What do you think? (add a timestamp, structure the response etc)

[pi0]

nuxt.config is safest place indeed (also please note consola should not be modified in other places. only use console.* calls)