Remove cache-loader and migrate on webpack@5 cache option

[matamatanot]

Feature request

ref: #12550
Remove cache-loader and migrate on webpack@5 the cache option.

Is your feature request related to a problem? Please describe.

When experimental option "babelMultiThread" is enabled, cache-loader is loaded.
But, the cache option of webpack@5 should be used instead.

x-ref: webpack-contrib/cache-loader#102 (comment)

Describe the solution you'd like

remove cache-loader.

Additional context

cache-loader, style-loader and file-loader depend on schema-utils. But, cache-loader no longer needed.

next.js/packages/next/taskfile.js

Lines 51 to 52 in e334c4e

	// dependents: cache-loader, style-loader, file-loader
	'schema-utils': 'schema-utils',

style-loader 2.0.0 depend on schema-utils 3.0.0.
https://github.com/webpack-contrib/style-loader/blob/256b1c38b6a729df3516e722173288d146676482/package.json#L48

next.js/packages/next/package.json

Line 113 in e334c4e

"style-loader": "1.2.1",

file-loader 6.1.1 depend on schema-utils 3.0.0.
https://github.com/webpack-contrib/file-loader/blob/14ed4c9b47f2e580f5b04b71f742cafe9e554565/package.json#L45

next.js/packages/next/package.json

Line 181 in e334c4e

"file-loader": "6.0.0",

So, schema-utils should be updated to 3.0.0.

next.js/packages/next/package.json

Line 111 in e334c4e

"schema-utils": "2.7.1",

After that, you can update postcss-loader to 4.0.4.
#17458 (comment)

updating postcss-loader to 4.0.4 breaks, because 4.0.4 requires schema-utils ^3.0.0, but the ncc build
prevents postcss-loader from using its own schema-utils

cc: @ludofischer 🙏 thanks!🙏

[matamatanot]

Close for next 12

[balazsorban44]

This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.