Issue with sass-embedded when the system runs out of resources about sass-loader HOT 5 CLOSED

Should be fixed by #1199, please update sass-loader to the latest stable versiob, i.e. 14.2.1, if it will not fix your problem need to wait an answer from sass-embedded, so feel free to feedback

from sass-loader.

According to my webpack-cli info, I believe I have 14.2.1 installed.

That aside, I have a question,
Looking at the commit there's a comment that says it should handle multi-threading more gracefully.
Does multi-threading mean the way of using webpack when the module exports multiple configurations?

If that's it it's how I am currently using webpack for running multiple configurations.

from sass-loader.

hm, do you want to share the one instance between processes?

from sass-loader.

hm, do you want to share the one instance between processes?

I believe it is beneficial for the speed of the build to have some parallel processes running, unless it uses too many resources. I was curious about what does it mean to run sass-loader in a multithreading way. In my previous comment, I said that I am running multiple configurations in parallel, these configurations are exported and then passed to webpack as described in webpack documentation.

https://webpack.js.org/configuration/configuration-types/#exporting-multiple-configurations

Each of these configurations have sass-loader enabled. Does it mean I am already running it in a multithreaded way?

from sass-loader.

hm, I am afraid it was not easy, we need to close sass compiler, so for each webpack compier we need to create one instance, I can improve the api option (make it a function, so you can manually create one compiler and share it), also perhaps it is worth raising the issue of why a lot of resources will be needed there in sass-embedded repo

from sass-loader.