Out of memory error

[busybox11]

Hello,
I am using this module since about a week and it's been flawless so far.
Though, today I tried optimizing my build by adding filesystem cache and CSS minification, and now all my builds fail with this error:

<--- Last few GCs --->

[48084:0x55e5eb19a940]   469585 ms: Mark-sweep 1979.7 (2093.9) -> 1977.5 (2086.4) MB, 329.3 / 0.0 ms  (average mu = 0.703, current mu = 0.162) allocation failure; scavenge might not succeed
[48084:0x55e5eb19a940]   470071 ms: Mark-sweep 2194.0 (2292.9) -> 1986.1 (2144.4) MB, 407.3 / 0.0 ms  (average mu = 0.561, current mu = 0.162) allocation failure; scavenge might not succeed


<--- JS stacktrace --->

FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
 1: 0x55e5e87d88f5 node::Abort() [webpack]
 2: 0x55e5e866a65a node::OnFatalError(char const*, char const*) [webpack]
 3: 0x55e5e89d3cba v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [webpack]
 4: 0x55e5e89d407b v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [webpack]
 5: 0x55e5e8b99a6a  [webpack]
 6: 0x55e5e8bb1a79 v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [webpack]
 7: 0x55e5e8b8c8d7 v8::internal::HeapAllocator::AllocateRawWithLightRetrySlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [webpack]
 8: 0x55e5e8b8dc69 v8::internal::HeapAllocator::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [webpack]
 9: 0x55e5e8b71e26 v8::internal::Factory::NewFillerObject(int, v8::internal::AllocationAlignment, v8::internal::AllocationType, v8::internal::AllocationOrigin) [webpack]
10: 0x55e5e8f04da9 v8::internal::Runtime_AllocateInYoungGeneration(int, unsigned long*, v8::internal::Isolate*) [webpack]
11: 0x55e5e93075f9  [webpack]
[1]    48073 IOT instruction (core dumped)  npm run build:prod

I know this module is causing the error thanks to the debugger, which tells me it's coming from plugin.js:41.
If I force the compilation via the debugger, bypassing the heap limit, it works just fine.
Is there something I can do to make this stop or do I really have to set a bigger heap?
Thanks in advance!