Expected behaviour

When I run karma, I get message valid_path/karma.conf.js, while the file it certainly there.

Actual behaviour

The error happens in this file:

File gets required successfully, but contains an inner require which fails.
Error handler sees the error type as MODULE_NOT_FOUND, but assumes that it's for outer, not inner require.

There's is actually a test for this:
&& e.message.includes(configFilePath)

But it fails because the path is in stack trace, which is part of the message.

Require stack:
- valid_path/karma.conf.js
....

Environment Details

• Karma version (output of karma --version):
  Karma version: 3.1.4
• Relevant part of your karma.config.js file

require('I do not exist');

Steps to reproduce the behaviour

1. create karma.conf.js, inside do:

require('I do not exist');

2. start karma
3. Get an error saying karma.config.js does not exist.