I hope this does not get deleted automatically, but https://nuxtjs.cmty.io/issues/new does not work!

Reproduction:

CodeSandbox: https://codesandbox.io/s/y0yxr7923j (unfortunately I can't get the CodeSandbox to run again after changing the nuxt.config.js and restarting. Please download the CodeSandbox and run locally to reproduce. Thx!)

1. Install Nuxt
2. Install and configure node-sass-magic-importer (see nuxt.config.js in CodeSandbox)
3. Run npm run generate
4. 100% CPU and nothing else happens (because the developers of global-prefix use try / catch without logging the error).

I've hunted down the error to the global-prefix package to the following lines: https://github.com/jonschlinkert/global-prefix/blob/master/index.js#L65

Add a console.error(err) in the catch section to see the Maximum call stack size exceeded error in node_modules/consola/dist/consola.js. Remove the try / catch block and just return null everything works fine.

Everything worked fine before Nuxt 2.5 so I assume something has changed with this package with the 2.5 release?

Thanks for the great work on Nuxt.js - I'm a big fan!

What problem does this feature solve?

Previous versions of consola exported all the internals which I used to create my own Consola instance in nuxt-generate-cluster: https://github.com/nuxt-community/nuxt-generate-cluster/blob/master/lib/utils/consola.js

Currently it seems the only export that is distributed is the consola instance. Which also means that the README is probably not correct. Eg when I log consola.JSONReporter it logs undefined (referring to this: https://github.com/nuxt/consola#creating-a-new-instance)

What does the proposed changes look like?

I'd also be happy with a third build file, eg so I have to import eg consola/dist/Consola to get access to all the exports in https://github.com/nuxt/consola/blob/master/src/index.js

Not sure what the best name for such an export would be

Version

v2.1.0

Reproduction link

https://codesandbox.io/s/r4kk7o5jl4?module=%2Fsrc%2Findex.ts&view=editor

Steps to reproduce

1. Create a TypeScript project.
2. Try logging an Error, number, or object.

What is expected ?

Consola types support logging with "any".

What is actually happening?

Consola only supports the string type.

Hello,
i´m trying to use the library in with Typescript but "consola" is undefined.

script.ts
import consola from "consola";
console.log(typeof consola);

tsconfig.json
{
"compilerOptions": {
"module": "commonjs",
"lib": ["es2015"],
"target": "es2015",
"experimentalDecorators": true,
"emitDecoratorMetadata": true,
"sourceMap": true,
"allowJs": true
}
}

Version

v2.1.0

Description

There are missing types for the following functions:

• create
• setReporters
• withTag
• withScope
• wrapAll
• restoreAll
• wrapConsole
• restoreConsole
• wrapStd
• restoreStd
• pauseLogs
• resumeLogs
• mockTypes

I have consola working with the default BasicReporter which is included in the JS file, however I can't work out how to use other reporters such as FancyReporter. None of the other reporters are installed using npm i consola.

Also should tags be displayed with BasicReporter? If so I can't get them to work.

Finally it would be great to see better documentation and an article on usage with examples would also be most welcome..

What problem does this feature solve?

I want to use consola in an express app written in TS, but for some reason definitions are excluded from final build published to NPM

Version

2.2.3

Reproduction link

https://codesandbox.io/s/vj522nv827

Steps to reproduce

• Use wrapAll
• Use any console.* method after that

What is expected ?

The log is enhanced

What is actually happening?

• The page crashes because of maximum call stack size exceeded.
• The browser reporter keeps on calling itself.

• Use Proxy instead of creating closures for each log type. This allows using arbitrary log types and less overhead of tagged loggers and easier mocking
• Find a way to make tagged loggers more lightweight when using withTag
• Deprecate withDefaults and create (Keep for legacy but create a new class instance`
• Support logs with timer (Using a token?)
• Seperate <type>(logOjb) from <type>(args. (How?)

It was partly too late I guess, I couldnt get it too work in nuxt-generate-cluster because there was still another Nuxt es6 import I missed it seems. After double checking to change all the nuxt imports to require's and add the cache delete after my own global.consola assignment it also works in the full project.

@pi0 @clarkdo Do you regards this a documentation issue or do you want to have a go at this to find a 'sexier' solution? If docs, I am happy to add something to the readme.

Why isnt it possibile (according to the docs) to auto-mocking consola with jest? The below example seems to work fine.
Also jest already supports methods for checking arguments, the following example does more or less the same as the current example. But as you know more than me, maybe I am missing something?

import consola from 'consola'

jest.mock('consola')

describe('consola', () => {
  beforeAll(() => {
    consola.wrapAll()
  })

  beforeEach(() => {
    jest.clearAllMocks()
  })

  test('is mocked', () => {
    consola.log('your message')

    expect(consola.log).toHaveBeenCalledWith('your message')
    expect(consola.log).toHaveBeenCalledTimes(1)
  })

  test('is mocked 2', () => {
    consola.log('your message 2')

    expect(consola.log).toHaveBeenCalledWith(expect.stringMatching(/message \d$/))
    expect(consola.log).toHaveBeenCalledTimes(1)
  })
})

What problem does this feature solve?

For large nested object (eg. Discord.js classes) consola doesn't have a level limit.

What does the proposed changes look like?

Add depth property to formatWithOptions

What problem does this feature solve?

It'd be great to have a few examples on how to mock consola (default, but also withScope) ☺️

We already have examples in the README, but a few more words to each wouldn't be bad ☺️

Although the docs say that consola is a global object, I cant get it too work correctly it seems. I have narrowed it down to module.exports which are cached.

// run as <file>.js
const { Consola, FancyReporter } = require('consola')

consola = new Consola({
  level: 4,
  reporters: [ new FancyReporter ],
  types: {
    warn: {
      level: 2,
      color: 'blue'
    },
  }
})

global.consola = consola

const consola2 = require('consola')
consola2.warn('yellow warning about nothing')

delete require.cache[require.resolve('consola')]

const consola3 = require('consola')
consola3.warn('blue warning about nothing')

The last consola3.warn is only blue when you delete the require.cache. This is because the first require already triggered node to cache the consola module, and as all other requires resolve to the same module/file it just uses the cached file.

The problem comes with esm modules like Nuxt has, the delete require.cache doesnt work there because during transpiling all requires are moved to the top of the file. Besides that, the delete require.cache trick only works when exactly:

• the delete happens after the custom global.consola assigment
• the require of Nuxt also happens after the custom global.consola assigment (and after the delete ofc)

// run with node -r esm <file.js>
console.log('mix -> works')
import consola from './inc/consola'
delete require.cache[require.resolve('consola')]

const { Nuxt } = require('nuxt')
const nuxt = new Nuxt()
nuxt.hook('render:context', () => {})
consola.warn('blue warning about nothing')

The following doesnt work:

// run with node -r esm <file.js>
import consola from './inc/consola'
delete require.cache[require.resolve('consola')]
import { Nuxt } from 'nuxt'

const nuxt = new Nuxt()
nuxt.hook('render:context', () => {})
consola.warn('blue warning about nothing')

import { Consola, FancyReporter } from 'consola'

let consola = global && global.consola

if (!consola) {
  consola = new Consola({
    level: 4,
    types: {
      warn: {
        level: 2,
        color: 'blue'
      },
    }
  })

  consola.add(new MyReporter())

  global.consola = consola
}

export default consola

Is it just too late and am I missing something obvious here? Any help / pointers are appreciated :)

Fyi, I am looking into this because for nuxt-generate-cluster I want all workers to push their log messages to the master so only the master has logging output. This does work nicely with a custom reporter, but I cant seem to capture the success: Generated /users/2 messages from within Nuxt.Generator. At least not without dirty tricks like re-assigning all object props again tp the global.consola object and stubbing the success method.

please reopen this issue.
https://github.com/nuxt/consola/issues/19

"@nuxtjs/axios": {

"version": "5.3.1",

"consola": {

"version": "1.4.1",

"std-env": {

"version": "1.3.1",

"is-ci": {

"version": "1.1.0",

"ci-info": {

"version": "1.1.3",

I'm using consola in a component by importing directly after the script-tag:

<script>
const consola = require("consola");
…

And then I use consola.start("Starting"); later on in a method.

I get the following error:

client.js:533 [nuxt] Error while initializing app ReferenceError: process is not defined
at Object../nodemodules/ci-info/index.js (index.js:3) at webpackrequire (bootstrap 9ce993297b8f99b86341:712)
at fn (bootstrap 9ce993297b8f99b86341:117)
at Object../nodemodules/is-ci/index.js (index.js:3) at webpackrequire (bootstrap 9ce993297b8f99b86341:712)
at fn (bootstrap 9ce993297b8f99b86341:117)
at Object.<anonymous> (index.js:1)
at Object../nodemodules/std-env/index.js (index.js:18) at webpackrequire (bootstrap 9ce993297b8f99b86341:712)
at fn (bootstrap 9ce993297b8f99b86341:117)

Version

1.3.0

Reproduction link

https://codepen.io/timyaodpc/pen/bMyazm

Steps to reproduce

Use it in Nuxt/plugins/myplugin.js.

It all works but in browser console it give me a error says "process is not defined". Error points to "ci-info" module first line which tries to use process.env.

I can see ci-info is a dependency of consola as below:

└─┬ [email protected]
└─┬ [email protected]
└─┬ [email protected]
└── [email protected]

I now have to add isServer condition on const consola = require('consola'). Otherwise it breaks the client side.

What is expected ?

Browser should no error in console.

What is actually happening?

A error from ci-info says "process is not defined".

index.js:3 Uncaught ReferenceError: process is not defined
at Object../nodemodules/ci-info/index.js (index.js:3) at webpackrequire (bootstrap 20212f6dd5b287d60bc9:712)
at fn (bootstrap 20212f6dd5b287d60bc9:117)
at Object../nodemodules/is-ci/index.js (index.js:3) at webpackrequire (bootstrap 20212f6dd5b287d60bc9:712)
at fn (bootstrap 20212f6dd5b287d60bc9:117)
at Object.<anonymous> (index.js:1)
at Object../nodemodules/std-env/index.js (index.js:18) at webpackrequire (bootstrap 20212f6dd5b287d60bc9:712)
at fn (bootstrap 20212f6dd5b287d60bc9:117)

Additional comments?

Is Consola can only be used in server side js?
The consola code index.js first line imported std-env which can only used in server side.
https://github.com/nuxt/consola/blob/master/src/index.js#L1
Not sure which is the best way to use it in Nuxt and maybe it's a bug?

Please remove it