-
Notifications
You must be signed in to change notification settings - Fork 111
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Workerize loader runs out of memory #108
Comments
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 |
It was using |
I had wroten here an error but its not the same, Im goint to create a new issue |
having same issue with |
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.
The text was updated successfully, but these errors were encountered: