The npm run serve command hides almost all logging

[palisadoes]

Describe the bug
The npm run serve command hides almost all logging

To Reproduce
Run the npm run serve command

Expected behavior
This behavior is not acceptable.

1. There is no feedback as to what is happening.
   1. There is no useful troubleshooting information shown
   2. There is no indication of the state of progress

Neither the development nor DevOps teams will therefore have the best information to troubleshoot issues. We require:

1. Full logging to the screen indicating what is happening
2. No clearing of the output between messages

Actual behavior

1. First this message is seen
   
2. Then the message is cleared, then this message is seen for a few seconds, then disappears
   
3. The screen then goes blank for several minutes with no indication of what is happening. The user may feel that the operation is failing.
4. This message is then displayed for several minutes with no indication of any activity happening
   
5. Finally, the screen clears once more then this message is visible
   

Additional details

• N/A

Potential internship candidates
Please read this if you are planning to apply for a Palisadoes Foundation internship PalisadoesFoundation/talawa#359

[Tarunmeena0901]

@palisadoes @noman2002 i will like to work on this issue,
thank you

[Tarunmeena0901]

hi @palisadoes @noman2002 i need little help here, the issue is almost solved as i had made changes in web.config.js and and integrate a state progress indicator in the console which shows the compilation progress and runtime error as well here are some screenshots

the only part left is to make is available for everyone but the changes made are in node_module/react-scripts/config/webpack.config.js
as we know we cannot commit node_module the how can make these changes commit in the repo

i thought of adding webpack.config.js in the root directory but it wont workt cause "npm run serve" command initiate the "react-scritps start" command (in package_json) .
can you help me with this please

[Tarunmeena0901]

ok so i came up with an solution in pull request . happy to take any suggestions

[github-actions]

This issue did not get any activity in the past 10 days and will be closed in 180 days if no update occurs. Please check if the develop branch has fixed it and report again or close the issue.