regression: 4.2.0 causes "Call retries were exceeded" with a fresh, blank Docusaurus project

[jamilbk]

Bug report

Actual Behavior

Upgrading to 4.2.0 causes the Call retries were exceeded with a fresh docusaurus project when npm run build is ran.

4.1.0 does not exhibit this issue.

Expected Behavior

Css should minimize without issue.

How Do We Reproduce?

npx create-docusaurus@latest my-website classic
cd my-website
npm run build

Observe the minimizer crash:

jamil@mbair:~/tmp/my-website % npm run build

> my-website@0.0.0 build
> docusaurus build

[INFO] [en] Creating an optimized production build...

✖ Client
  Compiled with some errors in 10.52s

● Server █████████████████████████ building (65%) 1/1 entries 1944/1944 dependencies 625/625 modules 0 active




assets/css/styles.45f640f6.css from Css Minimizer plugin
Error: Call retries were exceeded
assets/css/styles.8ef29f8a.css from Css Minimizer plugin
Error: Call retries were exceeded
[ERROR] Client bundle compiled with errors therefore further build is impossible.

Please paste the results of npx webpack-cli info here, and mention other relevant information

webpack-cli not relevant here

[alexander-akait]

Weird 😕 I will look at code, anyway if you found a workaround/problem feel free to send a PR

[sylvainbaronnet]

I got the same issue with 4.2.0, tried different minifier with same result

Edit : changing back to 4.1.0 fix it

[alexander-akait]

I think the problem in jest-worker, we need to check options and API usage

[danports]

Can confirm this regression on another project currently using 4.1.0 - builds using 4.2.0 are failing with the same Call retries were exceeded error.

[ttaylor29]

We are seeing this issue as well on Azure Pipeline.

Going back to 4.1.0. Will provide an update soon.

"css-minimizer-webpack-plugin": "4.1.0", 

UPDATE:

Worked for us!

[alexander-akait]

WIP on this

[alexander-akait]

@SimenB Friendly ping, looks like jest-worker is broken for standalone usage:

Error: Cannot find module 'jest-util'
Require stack:
- /home/akait/IdeaProjects/untitled/my-website/node_modules/jest-worker/build/workers/threadChild.js
    at Module._resolveFilename (node:internal/modules/cjs/loader:956:15)
    at Module._load (node:internal/modules/cjs/loader:804:27)
    at Module.require (node:internal/modules/cjs/loader:1022:19)
    at require (node:internal/modules/cjs/helpers:102:18)
    at _jestUtil (/home/akait/IdeaProjects/untitled/my-website/node_modules/jest-worker/build/workers/threadChild.js:14:16)
    at execFunction (/home/akait/IdeaProjects/untitled/my-website/node_modules/jest-worker/build/workers/threadChild.js:173:11)
    at execHelper (/home/akait/IdeaProjects/untitled/my-website/node_modules/jest-worker/build/workers/threadChild.js:151:5)
    at execMethod (/home/akait/IdeaProjects/untitled/my-website/node_modules/jest-worker/build/workers/threadChild.js:155:5)
    at MessagePort.messageListener (/home/akait/IdeaProjects/untitled/my-website/node_modules/jest-worker/build/workers/threadChild.js:59:7)
    at [nodejs.internal.kHybridDispatch] (node:internal/event_target:689:20) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [
    '/home/akait/IdeaProjects/untitled/my-website/node_modules/jest-worker/build/workers/threadChild.js'
  ]
}

Here usage - https://github.com/facebook/jest/blob/main/packages/jest-worker/src/workers/threadChild.ts#L9, but no in deps https://github.com/facebook/jest/blob/main/packages/jest-worker/package.json#L19

[alexander-akait]

Here fix - jestjs/jest#13341, but on the jest side

[zakariazuck]

Hi folks, I've come here for the same reason.
I'm doing some stuff with webpack and this error popped up.

This is not a fix, but I just went back to the most recent version @4.1.0 .

[alexander-akait]

When jestjs/jest#13341 was merged and jest-worker will released, just update your deps (transitive, i.e. rm -rf node_modules && npm i). If there is no reaction, I will downgrade the versions back

[ghost]

I tried removing the node_modules, package-lock.json and reinstalling everything. I'm still getting this error. Unfortunately, the project I'm working on is more than 6 years old with many (large) files, so I can't send something reproducible right away. I'll use 4.1.0 for now.

[jmsche]

Hi, a new tag was released for jest: https://github.com/facebook/jest/releases/tag/v29.1.2

After upgrading my vendors, the issue disappeared.

I think this issue can be closed :)

[SimenB]

Fix was released 40 minutes ago, sorry about the noise!

https://github.com/facebook/jest/releases/tag/v29.1.2

[SimenB]

I think this issue can be closed :)

Minimum version of jest-worker should probably be bumped to help consumers

[sylvainbaronnet]

I confirm it works now with new jest release. Thanks @alexander-akait

[NotMyFault]

Works fine on my end, thanks to everyone who was investigating into a fix!

[akshaybabloo]

can we have the minimum version of jest-worker updated here so that the dependabot can catch the update with a minor bump release?

[SimenB]

This was fixed by #199, but not released