fswatcher | cross-platform filewatcher library for c/c

It’s hitting your system's file watchers limit

Try echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p

Source

It seems like you still have processes from the old local server still hanging around and listening on those ports.

Make sure there is no serverprocess in taskmanager

try it:

Oh, I am going to answer my question after hours of my struggling.
The best solution is to install the latest version of Watchman.
The old version of Watchman causes fsevents module throws the exception.

After installing watchman, optionally you can run sudo chown -R $(whoami):staff ~/Library/LaunchAgents to give the permission.

As increasing the limit didn't work for me, I tried a different approach. I didn't add my node_modules files to the watcher.

From my experience the best fix would be to expose the watcher configuration where one could define to ignore any folders or files of their choosing, not just node_modules.

You seem to be running configure from "msys" subsystem of MSYS2 which is a POSIX-like system not meant to be used for compilation.

You should launch mingw64.exe or mingw32.exe instead to build native MSW software using MinGW and then configure should work just fine there.

The problem was in the text editor and its methods of working with the file.

I ran into this same problem recently. I solved it like this:

So something you could do is create the build file and then serve the static files in the directory with a tiny local server.

You could run the yarn build then have a script that runs this code yarn node ./server.js (or whatever you name it)

This could allow for the performant builds and the server similar to the DevServer that react-scripts start server.

I also don't know if you need profiling in production but I added a feature on react-scripts build --profile that allows classnames and functions names to persist through the terser.