What problem does this feature solve?

It is sometimes required to have a more fine grain control over log level per reporter.
For instance, let's say we want the stdout reporter to only show info log lever, but at the same time write trace log level to a file using the json reporter.

What does the proposed changes look like?

We need to enable each reporter to have a log level override and when logging occurs, only operate on the relevant loggers

I would like to change output from Nuxt.js to json log format.
Is there a way?

Version

v2.11.3

Reproduction link

https://example.com

Steps to reproduce

import { Consola, FancyReporter } from 'consola';
will produce an error as there is no exported member FancyReporter

What is expected ?

to have proper detentions for the entire library

What is actually happening?

typescript error

The code:

const consola = require('consola')

consola. // *CTRL+Space*

Instead of

Please fix the typing

Ref: #80

Fix a typing issue that causes this to throw a typing error on consola.green:

// @ts-check

const consola = require('consola')

consola.green('foo')

Workaround:

// globals.d.ts

import { Consola } from 'consola'

declare module 'consola' {
  export = new Consola()
}

Version

v2.11.2

Reproduction link

https://jsfiddle.net/6hj9wd35/

Steps to reproduce

Run a project with latest version

What is expected ?

Remove incorrect export, line 98
https://github.com/nuxt/consola/commit/5c22d8cd4624e3bbd7294b9eba09f131ed786332

What is actually happening?

An export assignment cannot be used in a module with other exported elements.

ERROR in ./node_modules/consola/types/consola.d.ts(98,1):                                                          nuxt:typescript 11:30:28
   96 | export default consolaGlobalInstance
   97 | 
 > 98 | export = consolaGlobalInstance
      | ^
   99 | 
ℹ Version: typescript 3.7.4                                                                                                                                nuxt:typescript 11:30:28
ℹ Time: 15081ms                                                                                                                                            nuxt:typescript 11:30:28
ℹ Waiting for file changes                                                                                                                                                 11:30:28
ℹ Memory usage: 638 MB (RSS: 1.23 GB) 

how to solve this problem
ERROR in D:/web/test-nuxt-ts/nodemodules/consola/types/consola.d.ts ERROR in D:/web/test-nuxt-ts/nodemodules/consola/types/consola.d.ts(98,1):
98:1 An export assignment cannot be used in a module with other exported elements.
96 | export default consolaGlobalInstance
97 |

98 | export = consolaGlobalInstance
| ^
99 |

FATAL Nuxt build error

ERROR in f:/web/explorer/node_modules/consola/types/consola.d.ts
ERROR in f:/web/explorer/node_modules/consola/types/consola.d.ts(98,1):
98:1 An export assignment cannot be used in a module with other exported elements.
    96 | export default consolaGlobalInstance
    97 | 
  > 98 | export = consolaGlobalInstance
       | ^
    99 | 

 FATAL  Nuxt build error                                                                                                                                                                             15:42:59

  at WebpackBundler.webpackCompile (node_modules\@nuxt\webpack\dist\webpack.js:5326:21)
  at process._tickCallback (internal/process/next_tick.js:68:7)


   ╭─────────────────────────────╮
   │                             │
   │   ✖ Nuxt Fatal Error        │
   │                             │
   │   Error: Nuxt build error   │
   │                             │
   ╰─────────────────────────────╯

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] generate: `nuxt generate`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] generate script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

ERROR  ERROR in ./node_modules/consola/types/consola.d.ts(98,1):                                                          nuxt:typescript 11:30:28
98:1 An export assignment cannot be used in a module with other exported elements.
    96 | export default consolaGlobalInstance
    97 | 
  > 98 | export = consolaGlobalInstance
       | ^
    99 | 

ℹ Version: typescript 3.7.4                                                                                                                                nuxt:typescript 11:30:28
ℹ Time: 15081ms                                                                                                                                            nuxt:typescript 11:30:28
ℹ Waiting for file changes                                                                                                                                                 11:30:28
ℹ Memory usage: 638 MB (RSS: 1.23 GB)    

Version

v2.11.2

Reproduction link

https://codesandbox.io/s/gracious-mendel-uw0vh

Steps to reproduce

Functions like setTimeout and clearTimeout are not defined on https://developer.mozilla.org/en-US/docs/Web/API/AudioWorkletGlobalScope

Logging with consola uses these functions in order to throttle logging. It should be possible to disable the throttling or have consola disable throttling if these functions are not available.

Creating a worklet.js file with the following code:
console.log({setTimeout: typeof setTimeout, clearTimeout: typeof clearTimeout})

And another file, index.js with the following:
new AudioContext().audioWorklet.addModule("/worklet.js")

Outputs
{setTimeout: "undefined", clearTimeout: "undefined"}

What is expected ?

Consola to log without a crash

What is actually happening?

Consola code crashes

Version

v2.10.0

Reproduction link

https://repl.it/repls/RealDarkredOolanguage

Steps to reproduce

Create deeply (4 levels) nested object and try to log it.

What is expected ?

Whole object gets logged in the console.

What is actually happening?

Object is collapsed and part of it becomes simply [Object] hiding important info.

Additional comments?

This could be a configurable behaviour but I strongly belive that by default everything should be visible.

Version

v2.10.0

Reproduction link

https://jsfiddle.net/boilerplate/vue

Steps to reproduce

Hello.

I have installed consola in my project and when I click on a nuxt-link who must display a log via Middleware I have an error : consola.info is not a function

If I refresh the page with my browser the log works well.

PS : an other project with nuxt 2.5.0 and consola 2.5.7 was working well

• My middleware/log-router.js file

const consola = require('consola')

export default function (context) {
  consola.info('--> Info | request ' + context.route.fullPath + ' launched')
}

• My nuxt.config.js file

export default {
  ...
  router: {
    // Run the middleware/log-router.js on every page
    middleware: 'log-router'
  }
}

What is expected ?

Log a message

What is actually happening?

Blank page with error.

• Page :
  consola.info is not a function
  An error occurred while rendering the page. Check developer tools console for details.

• Console :
  vendors.app.js:11254 error TypeError: consola.info is not a function
  at app.js:3989
  at promisify (app.js:3422)
  at middlewareSeries (app.js:3401)
  at Vue.callMiddleware (app.js:943)
  at Vue._callee4$ (app.js:1069)
  at tryCatch (commons.app.js:6116)
  at Generator.invoke as _invoke
  at Generator.prototype.<computed> as next
  at asyncGeneratorStep (commons.app.js:31)
  at _next (commons.app.js:53)
  log @ vendors.app.js:11254
  _log @ vendors.app.js:11166
  logFn @ vendors.app.js:11160 logFn @ vendors.app.js:11084 push../.nuxt/client.js.vueWEBPACKIMPORTEDMODULE18.default.config.errorHandler @ app.js:680
  globalHandleError @ app.js:3101
  _callee4$ @ app.js:1319
  tryCatch @ commons.app.js:6116
  invoke @ commons.app.js:6342
  prototype.<computed> @ commons.app.js:6168
  asyncGeneratorStep @ commons.app.js:31
  _next @ commons.app.js:53
  Promise.then (async)
  asyncGeneratorStep @ commons.app.js:41
  _next @ commons.app.js:53
  (anonymous) @ commons.app.js:60
  (anonymous) @ commons.app.js:49
  _render @ app.js:1342
  render @ app.js:947
  iterator @ commons.app.js:10678
  step @ commons.app.js:10452
  (anonymous) @ commons.app.js:10453
  (anonymous) @ commons.app.js:10699
  _callee3$ @ app.js:805
  tryCatch @ commons.app.js:6116
  invoke @ commons.app.js:6342
  prototype.<computed> @ commons.app.js:6168
  asyncGeneratorStep @ commons.app.js:31
  _next @ commons.app.js:53
  (anonymous) @ commons.app.js:60
  (anonymous) @ commons.app.js:49
  loadAsyncComponents @ app.js:842 loadAsyncComponents @ app.js:736 iterator @ commons.app.js:10678 step @ commons.app.js:10452 step @ commons.app.js:10456 runQueue @ commons.app.js:10460 confirmTransition @ commons.app.js:10707 transitionTo @ commons.app.js:10609 push @ commons.app.js:10919 push @ commons.app.js:11300 handler @ commons.app.js:9174 invokeWithErrorHandling @ commons.app.js:13255 invoker @ commons.app.js:13580 original.wrapper @ commons.app.js:18303
  Show 14 more frames

The repeated X times is only triggered with a trailing consola call. If you dont have a trailing consola call the spam message doesnt get printed.

See https://jsfiddle.net/6pvqxy1k/1/ for an example, without the END call the (repeated 4 times) message will never be printed

import consola from 'consola'

const logger = consola.create({
// level: 4,
reporters: new consola.JSONReporter() ,
defaults: {
additionalColor: 'white'
}
})

Error TS2339 (TS) Property 'JSONReporter' does not exist on type 'Consola'.
Error TS2322 (TS) Type '{ additionalColor: string; }' is not assignable to type 'ConsolaLogObject'.
Object literal may only specify known properties, and 'additionalColor' does not exist in type 'ConsolaLogObject'.
i'm using code in document, but it have error. i don't nkow how to fix it. pls help me, thanks you very much.

Version

v2.10.0

Reproduction link

https://codesandbox.io/embed/fervent-pine-su2ty

Steps to reproduce

Hi folks,

Consola is not handling the native string substitutions of console.
https://developer.mozilla.org/en-US/docs/Web/API/console#Using_string_substitutions

This leads to issues when when using wrapConsole method in code bases where you don't control logs.

Example: there is a problem with all the react errors.

Here an example before/after the wrap:

- Warning: Received `true` for a non-boolean attribute `secondary`.
+ Warning: Received `%s` for a non-boolean attribute `%s`.

- If you want to write it to the DOM, pass a string instead: secondary="true" or secondary={value.toString()}.
+ If you want to write it to the DOM, pass a string instead: %s="%s" or %s={value.toString()}.%s true secondary secondary true secondary 
    in h1 (created by App)
    in div (created by App)
    in App

For me, consola should have the same api than console, to be able to replace it properly.

How can we handle that?

Thanks for your work,
Matt'.

What is expected ?

Consola should have at least the same api and features than console.

What is actually happening?

Features from console are missing in consola (browser and node).

The project is almost an example of js. Can you provide an example of ts? thank you very much

The project is almost an example of js. Can you provide an example of ts? thank you very much