Thank you for building a very useful bundle.
When I run the dev-server, it takes a lot of memory. One thing I noticed is that there is a PHP process that takes a lot of memory on top of the webpack process. Now, for the webpack process ofcourse there is nothing you can do, but I was thinking, could we either optimize or kill the PHP process? Maybe there could be a console option that if we pass to the maba:dev-server command, the process would start webpack, and exit. And then to kill the webpack process we would either do that manually, or maybe introduce a new command.
Is this something that is possible, or is the PHP process in the background necessary?
Hello,
Thank you for building a very useful bundle. When I run the dev-server, it takes a lot of memory. One thing I noticed is that there is a PHP process that takes a lot of memory on top of the webpack process. Now, for the webpack process ofcourse there is nothing you can do, but I was thinking, could we either optimize or kill the PHP process? Maybe there could be a console option that if we pass to the maba:dev-server command, the process would start webpack, and exit. And then to kill the webpack process we would either do that manually, or maybe introduce a new command.
Is this something that is possible, or is the PHP process in the background necessary?