Open TeoTN opened 4 years ago
Sorry for the late reply. In order to know what's going on, I'd need to know if you're enabling Workerize-loader using inline loader syntax, or via module.rules mappings in your Webpack configuration.
Sorry for the late reply. In order to know what's going on, I'd need to know if you're enabling Workerize-loader using inline loader syntax, or via module.rules mappings in your Webpack configuration.
I have the same problem with using an inline loader
Sorry for the late reply. In order to know what's going on, I'd need to know if you're enabling Workerize-loader using inline loader syntax, or via module.rules mappings in your Webpack configuration.
It was using module.rules
mappings in webpack config. I don't work on that project anymore though (don't have access), so won't be able to provide much more details, unfortunately
I had wroten here an error but its not the same, Im goint to create a new issue
having same issue with workerize-loader:2.0.2
on webpack 5 via module.rules config. It seems working fine with inline loader syntax though.
Workerize loader runs out of memory in my custom webpack config (unfortunately, I can't share it), and I see similar issue to this one.
when running
webpack --progress
, it doesn't stop on any particular file, it's usually around 67% though.workerize-loader
is in version 1.3.0webpack
is4.43.0
Would you be able to suggest how to debug this issue? I was trying to compare my config with CRA, and the only major difference is that CRA is running TypeScript in fork, I wonder if this may be an important difference.