I ran a build successfully this morning and when I went to build it again I got this error. Not sure what's going on.
I ran npm start and it had no problem running on my localhost and the website functions 100%.
Creating an optimized production build...
<--- Last few GCs --->
[19110:0x110008000] 34076 ms: Mark-sweep 1381.1 (1446.9) -> 1371.8 (1449.4) MB, 327.1 / 0.0 ms (average mu = 0.222, current mu = 0.159) allocation failure scavenge might not succeed
[19110:0x110008000] 34473 ms: Mark-sweep 1383.9 (1449.4) -> 1374.5 (1452.9) MB, 318.0 / 0.0 ms (average mu = 0.210, current mu = 0.197) allocation failure scavenge might not succeed
<--- JS stacktrace --->
==== JS stack trace =========================================
0: ExitFrame [pc: 0x197557b5be3d]
1: StubFrame [pc: 0x197557b52da6]
Security context: 0x12993291e6e1 <JSObject>
2: split [0x1299329106c1](this=0x12999fc96061 <String[132]: /Users/nnannanwadike/Downloads/cannago-website-master/node_modules/react-star-ratings/node_modules/react/cjs/react.production.min.js>,0x12992aa57931 <JSRegExp <String[3]: \/+>>)
3: normalize [0x1299b4504bd9] [/Users/nnannanwadike/Downloads/cannago-websit...
FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
1: 0x10003ae75 node::Abort() [/usr/local/bin/node]
2: 0x10003b07f node::OnFatalError(char const*, char const*) [/usr/local/bin/node]
3: 0x1001a7ad5 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [/usr/local/bin/node]
4: 0x100572ee2 v8::internal::Heap::FatalProcessOutOfMemory(char const*) [/usr/local/bin/node]
5: 0x1005759b5 v8::internal::Heap::CheckIneffectiveMarkCompact(unsigned long, double) [/usr/local/bin/node]
6: 0x10057185f v8::internal::Heap::PerformGarbageCollection(v8::internal::GarbageCollector, v8::GCCallbackFlags) [/usr/local/bin/node]
7: 0x10056fa34 v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [/usr/local/bin/node]
8: 0x10057c2cc v8::internal::Heap::AllocateRawWithLigthRetry(int, v8::internal::AllocationSpace, v8::internal::AllocationAlignment) [/usr/local/bin/node]
9: 0x10057c34f v8::internal::Heap::AllocateRawWithRetryOrFail(int, v8::internal::AllocationSpace, v8::internal::AllocationAlignment) [/usr/local/bin/node]
10: 0x10054bc94 v8::internal::Factory::NewFillerObject(int, bool, v8::internal::AllocationSpace) [/usr/local/bin/node]
11: 0x1007d3b44 v8::internal::Runtime_AllocateInNewSpace(int, v8::internal::Object**, v8::internal::Isolate*) [/usr/local/bin/node]
12: 0x197557b5be3d
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! react-lp@0.1.0 build: `react-scripts build`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the react-lp@0.1.0 build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /Users/nnannanwadike/.npm/_logs/2022-02-23T20_12_35_918Z-debug.log```
