How to print console.log statements in tests to test output in terminal

[jhhom]

Hi, thanks for the great extension.

One problem I'm facing is if I have a console.log statements in my tests, it doesn't get outputted to the terminal, compared to the command npx vitest which does output console.log statements in terminal

My setting for vitest.commandLine is npx vitest --watch.

Here is the test output I'm getting when running the extension. May I know how to get the log statements printed to test output?

This is what I get from running npx vitest instead, which does print the console.log statements

What I found is if I changed the viteset.commandLine setting to npx vitest -- instead, it will show the console log output, however the extension will hang on the test and never finished as the command "Wait for file changes" forever.

So is it possible to get the console log outputs with the npx vitest --watch command? Or how to make the extension works properly while still getting the console log statements printed on the terminal?

[jossephus]

It's been sometime but for anyone facing the same problem, you can set --silent=false when running vitest to get console outputs.

[castarco]

This does not work at all.

[jhhom]

Is this setting correct? I'm still not getting the console outputs on my terminal from running the test using the extension

[snuup]

No results here as well. Can someone please help us?

[DanTup]

I just hit this too.. I found --disable-console-intercept documented on https://vitest.dev/guide/cli which seems to be working for me.

[tankorsmash]

Worked for me, thank you!

pnpx vitest --inspect-brk --no-file-parallelism --disable-console-intercept 

[tomardern]

Worked for me too! thanks :)

[RangerMauve]

I found that with the default reporter it swallows any output anyways. Using --reporter=json along with --disable-console-intercept worked.

[kevireilly]

Appears as though you can also use --reporter=basic --disable-console-intercept to get the same default reporter output while including console output.

[iamsalmakolkari]

Vitest provides a configuration method called onConsoleLog which is Custom handler for console.log in tests. It is basically used if you want to supress logs based on the message text. So, if you want to see console logs add below code in vitest.config.ts.

/// <reference types="vitest" />
import { defineConfig, mergeConfig } from 'vitest/config';
import viteConfig from './vite.config';

export default mergeConfig(
  viteConfig({ command: 'build', mode: 'TEST' }),
  defineConfig({
    test: {
      coverage: {
        exclude: ['src/api'],
        include: ['src'],
      },
      environment: 'jsdom',
      globals: true,
      setupFiles: './setupTests.ts',
      onConsoleLog(log: string, type: 'stdout' | 'stderr'): false | void {
        console.log('log in test: ', log);
        if (log === 'message from third party library' && type === 'stdout') {
          return false;
        }
      },
    },
  }),
);

Quick note: If you have spied on console.log for testing any scenarios in your test case, then the spy will swallow the logs and no log in your test case will be printed to terminal.

[Caalb]

In my vitest.config.js I had a config called pool: ‘vmThreads’, removing it I was able to display the consoles correctly

[christophemarois]

Trick for certain situations: if you're just trying to get something printed to stdout, process.stdout.write() will work.

[pgraham-calix]

Appreciate all of the work arounds, but I think it would be an important (maybe necessary) feature of a test runner to be able to just log output without having to mess with config.

[pgraham-calix]

Actually, looks like it does work out of the box, I just missed what I was longing amongst the rest of the output.

[sheremet-va]

The extension does print the output. In fact, it only prints the user's output, ignoring the Vitest CLI reporting

[balch-dev]

For anybody stuck using vitest v1.x, you can use --silent=true --reporter=basic as the default reporter collapses the output of your previous tests.

[albertreed]

There are several answers here - none of which seem to be working for me. Is there a definitive way to enable console.log() printing? As a previous poster mentioned, this feels like an essential thing to allow.