I cloned a fresh copy of the repo and was able to build and run the app without error. Since frontend is mostly Create React App boilerplate, which handles all the Webpack configuration, the source of the problem is hidden under all of CRA's magic.
Assuming you didn't eject CRA or move files into or out of public, it's possible that old packages are causing problems, as I haven't updated any of them since writing the post. Try updating CRA to the latest version.
This issue started with the v3.4.1 upgrade, I listed 5-6 ways from this thread on how to fix it, from pinning to the 3.4.0 version, changing docker-compose up to docker-compose run.. for now I've settled adding a terminal to my compose file, but someone else pointed out the reason they closed the terminal is it could be a security risk. Ultimately the issue is when docker has the server running it thinks it's completed the job and exits.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I cloned a fresh copy of the repo and was able to build and run the app without error. Since
frontendis mostly Create React App boilerplate, which handles all the Webpack configuration, the source of the problem is hidden under all of CRA's magic.Assuming you didn't eject CRA or move files into or out of
public, it's possible that old packages are causing problems, as I haven't updated any of them since writing the post. Try updating CRA to the latest version.issues/8688
This issue started with the v3.4.1 upgrade, I listed 5-6 ways from this thread on how to fix it, from pinning to the 3.4.0 version, changing
docker-compose uptodocker-compose run.. for now I've settled adding a terminal to my compose file, but someone else pointed out the reason they closed the terminal is it could be a security risk. Ultimately the issue is when docker has the server running it thinks it's completed the job and exits.