Unknown cause for memory balloon with NPM install

[ReyBernDia]

Reported app memory size went from ~150MB to between 512MB and 1GB from the npm package.

Here are the logs around this:

2022-03-10T16:30:32.011166+00:00 heroku[web.1]: State changed from crashed to starting
2022-03-10T16:30:42.538197+00:00 heroku[web.1]: Starting process with command `npm run prod`
2022-03-10T16:30:44.638422+00:00 app[web.1]: 
2022-03-10T16:30:44.638433+00:00 app[web.1]: > prod
2022-03-10T16:30:44.638434+00:00 app[web.1]: > npm run build && npm run server:prod
2022-03-10T16:30:44.638434+00:00 app[web.1]: 
2022-03-10T16:30:45.094949+00:00 app[web.1]: 
2022-03-10T16:30:45.094969+00:00 app[web.1]: > build
2022-03-10T16:30:45.094971+00:00 app[web.1]: > vite build && vite build --ssr
2022-03-10T16:30:45.094972+00:00 app[web.1]: 
2022-03-10T16:30:45.634780+00:00 app[web.1]: vite v2.8.6 building for production...
2022-03-10T16:30:45.766871+00:00 app[web.1]: transforming...
2022-03-10T16:31:02.639128+00:00 app[web.1]: ✓ 1189 modules transformed.
2022-03-10T16:31:06.672793+00:00 app[web.1]: rendering chunks...
2022-03-10T16:31:09.076933+00:00 app[web.1]: 
2022-03-10T16:31:09.076952+00:00 app[web.1]: <--- Last few GCs --->
2022-03-10T16:31:09.076952+00:00 app[web.1]: 
2022-03-10T16:31:09.076953+00:00 app[web.1]: [34:0x53857b0]    23964 ms: Mark-sweep (reduce) 251.2 (258.6) -> 250.5 (259.1) MB, 440.5 / 0.0 ms  (+ 0.0 ms in 0 steps since start of marking, biggest step 0.0 ms, walltime since start of marking 444 ms) (average mu = 0.109, current mu = 0.033) allocatio
2022-03-10T16:31:09.076958+00:00 app[web.1]: 
2022-03-10T16:31:09.076959+00:00 app[web.1]: <--- JS stacktrace --->
2022-03-10T16:31:09.076959+00:00 app[web.1]: 
2022-03-10T16:31:09.076959+00:00 app[web.1]: FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
2022-03-10T16:31:09.077844+00:00 app[web.1]:  1: 0xb09980 node::Abort() [node]
2022-03-10T16:31:09.078456+00:00 app[web.1]:  2: 0xa1c235 node::FatalError(char const*, char const*) [node]
2022-03-10T16:31:09.079134+00:00 app[web.1]:  3: 0xcf77be v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [node]
2022-03-10T16:31:09.083341+00:00 app[web.1]:  4: 0xcf7b37 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [node]
2022-03-10T16:31:09.084162+00:00 app[web.1]:  5: 0xeaf3d5  [node]
2022-03-10T16:31:09.084959+00:00 app[web.1]:  6: 0xebf09d v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [node]
2022-03-10T16:31:09.085784+00:00 app[web.1]:  7: 0xec1d9e v8::internal::Heap::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [node]
2022-03-10T16:31:09.086515+00:00 app[web.1]:  8: 0xe832da v8::internal::Factory::NewFillerObject(int, bool, v8::internal::AllocationType, v8::internal::AllocationOrigin) [node]
2022-03-10T16:31:09.087361+00:00 app[web.1]:  9: 0x11fc026 v8::internal::Runtime_AllocateInYoungGeneration(int, unsigned long*, v8::internal::Isolate*) [node]
2022-03-10T16:31:09.088344+00:00 app[web.1]: 10: 0x15f0a99  [node]
2022-03-10T16:31:09.119344+00:00 app[web.1]: Aborted
2022-03-10T16:31:09.277621+00:00 heroku[web.1]: Process exited with status 134
2022-03-10T16:31:09.346323+00:00 heroku[web.1]: State changed from starting to crashed

This is an issue for apps deployed to a server with low RAM. For the reporting user, this was not an issue locally because their computer had more RAM than the heroku server hosting their app.
This is probably going to be an issue for other users of this scheduler as well.