jest crashes after upgrade to v12

[fterlid]

After upgrading jest from v11.0.2 to v12, jest crashes immidiately. I'm using a gulp task for running tests. Stack trace:

[13:16:19] Using gulpfile C:\x\gulpfile.js
[13:16:19] Starting 'test'...
Using Jest CLI v12.0.2, jasmine2
TypeError: Not a string or buffer
    at TypeError (native)
    at Hash.update (crypto.js:70:16)
    at C:\x\node_modules\jest-haste-map\src\index.js:148:56
    at Array.forEach (native)
    at Function.getCacheFilePath (C:\x\node_modules\jest-haste-map\src\index.js:148:36)
    at new HasteMap (C:\x\node_modules\jest-haste-map\src\index.js:132:32)
    at createHasteMap (C:\x\node_modules\jest-cli\src\lib\createHasteMap.js:21:10)
    at new TestRunner (C:\x\node_modules\jest-cli\src\TestRunner.js:60:22)
    at runJest (C:\x\node_modules\jest-cli\src\jest.js:150:22)
    at C:\x\node_modules\jest-cli\src\jest.js:245:16

Any ideas? The gulp file is unchanged and worked with v11. The gulp task looks like this:

gulp.task('test', function(done) {
    var jestConfig = {
        rootDir: 'src'
        scriptPreprocessor: '../node_modules/babel-jest',
        unmockedModulePathPatterns: [/*shortened for brevity*/],
        noStackTrace: true,
        verbose: false,
        testFileExtensions: ['test.js']
    };

    jest.runCLI({ config: jestConfig }, './src', function() { done(); });
});

[atecarlos]

There seems to be an expectation of a name property in the config. It eventually ends up as undefined which causes this error. Adding a name property to your config will let your tests run.

[fterlid]

Great, @atecarlos, thanks! I set name to an empty string, and everything seems to work.

I guess there is some documentation and a default value missing.

[fterlid]

It seems the name property is picked up from the top-level of package.json when the jest config is stored there. When running jest with e.g. gulp or with the --config option, if the name property is not defined, it will crash.

Would it make sense to set a default value to name? I'm thinking an empty string would be appropriate. It looks like it is used as a filename prefix for cache files, so a more specific default string like 'default-name' migth make for some strange file names.

[cpojer]

We fixed this for the next release :)

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.