rmarcelo
rmarcelo
Just sharing my workaround for CRA 5.0 ```javascript // setup.js const fs = require('fs'); const path = require('path'); if (process.env.NODE_ENV === 'development') { const webPackConfigFile = path.resolve('./node_modules/react-scripts/config/webpack.config.js'); let webPackConfigFileText =...
> ws://localhost:3000/ws @Makentosh This is a different issue, but I've experience that error also, looking at your docker file, it seems that you should be using port 9999, you can...
@Makentosh How do you access it in the browser? do you use reverse proxy? could you try WDS_SOCKET_PORT=0 ?
> @rmarcelo in browser get http://localhost:9999/ > > WDS_SOCKET_PORT=0 also does not work > > log in docker > > audited 1272 packages in 6.062s > > > 169 packages...
> @rmarcelo There is no error, but hot reload does not work The setup.js that I posted has this, maybe you're not getting development on your NODE_ENV, try to remove...
@Makentosh did your webpack.configs.php became like this at the bottom? 
@Makentosh can you show us what your webpack.config.js looks like at the performance: false, ? wrong filename reference on my previous comment
@Makentosh hmm, that's weird, I don't see any reason why it should not work anymore on your end, the setup.js should trigger on npm start or yarn start which would...
@Makentosh you can remove the ```if (process.env.NODE_ENV === 'development') {}``` , I just put it there since I'm also using the setup.js for my ```npm build```