You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Cannot read properties of undefined (reading 'util')
at PoolWorker.fromErrorObj (/some_dir/node_modules/thread-loader/dist/WorkerPool.js:302:12)
at /some_dir/node_modules/thread-loader/dist/WorkerPool.js:184:29
at /some_dir/foo/bar/file.less:1:1
at defaultGetLocalIdent (/some_dir/node_modules/css-loader/dist/utils.js:323:37)
Code
css-loader expects to be able to create hashes via an exposed loader/webpack api. thread-loader doesn't expose these over the processes bridge so hitting this code will always errror.
How Do We Reproduce?
Specifying any of the localIdent configuration options on css-loader and running it in thread-loader should be enough to repro.
Additional questions
I reported this as a bug since it seemed previously compatibility with css-loader was intended. If that's still the case, is there a better way for them to create hashes?
The text was updated successfully, but these errors were encountered:
issacgerges
changed the title
Incompatibility with css-loader
Incompatibility with css-loader due to its use of createHash
Mar 18, 2024
20
10.5.0
5.90.3
4.0.2
Expected Behavior
thread-loader
is compatible withcss-loader
Actual Behavior
The following exception is raised at runtime
Code
css-loader
expects to be able to create hashes via an exposed loader/webpack api.thread-loader
doesn't expose these over the processes bridge so hitting this code will always errror.How Do We Reproduce?
Specifying any of the
localIdent
configuration options oncss-loader
and running it inthread-loader
should be enough to repro.Additional questions
I reported this as a bug since it seemed previously compatibility with
css-loader
was intended. If that's still the case, is there a better way for them to create hashes?The text was updated successfully, but these errors were encountered: