`wasp start` takes a lot of memory (~1 GB) to run frontend

[Martinsos]

We noticed that wasp start takes about 1GB of memory(RAM).
That seemed a lot, so I tested a bit more, by running npm start in .wasp/out for server and frontend.
It turns out, server spends almost no memory, while frontend is the one that consumes almost 1GB of it.
So the question is, why does frontend consume so much of it, and how we can we avoid this?

We should try to improve this and have frontend spend less memory.
This would make wasp a lighter process to run on devs machines, but would also help a lot with running it in cloud environments like Replit where memory is quite limited.

[Martinsos]

Is it CRA causing that? Can we get it to not do it? Should we switch to Vite?

[EmmanuelTheCoder]

What version of CRA is Wasp on?

This issue might help give a headstart to solving the problem facebook/create-react-app#10119
Someone in the comments mentioned disabling Eslint.

[Martinsos]

This SO mentions ideas:

1. Limit RAM consumption by setting some flag
2. Turn off sourcemap generation

https://stackoverflow.com/questions/57762452/react-scripts-build-is-using-1-gb-of-ram

[Martinsos]

5.0.1!

They mention source maps and eslint, so worth checking both of those!

[Martinsos]

Related: #640 .

[Martinsos]

We switched to Vite and this is much better now, it takes maybe 200, 300mb, instead of 1GB. It is still more than server, which takes almost nothing, but I think this is ok for now.