How to get verbose output when running npm test command on packages?

Other Questions NPM
1

I’m having trouble with npm test command not showing enough information when testing packages. When I run the test command on a specific package, it works fine but doesn’t display any output when the test passes successfully.

# npm test mypackage

The command only shows error messages like ‘npm is not ok’ when there are problems with the package, but stays completely silent when everything works correctly. This makes it hard to know if the test actually ran or what happened during the process.

I’ve been looking for ways to make the test command more verbose so I can see what’s happening behind the scenes. Is there a flag or configuration option that can enable detailed logging for npm test operations? I want to see the test output even when tests pass successfully.

2

hey, have you tried using the --verbose flag? it gives more info. also, running npm test -- --verbose might help. setting npm config set loglevel verbose before tests can show all the details too.

3

Had this exact problem last year on a big multi-package project. The issue is npm test inherits npm’s logging behavior, which defaults to minimal output. Try npm test --loglevel=silly - it shows everything including the actual commands being run. You can also use npm run test -- followed by your test runner flags. With Jest, I’d do npm run test -- --verbose --coverage for detailed output. Check your package.json test script too - make sure it’s not redirecting to /dev/null or using quiet flags. If you think output is getting lost, try npm test 2>&1 to capture both stdout and stderr.

4

npm test runs silently by default and won’t display standard output. You can resolve this by trying npm test --silent=false or npm run test --silent=false. Additionally, using npm test --loglevel=info can provide more details about the execution process. Ensure to check your package.json test script as it may be configured to redirect output or utilize a test runner that suppresses console logs. For frameworks like Jest or Mocha, they often have their own verbose flags that can be applied.