ERR_EMPTY_RESPONSE #109

Activity

1. andrewngu commented on Aug 11, 2017

   

   andrewngu

   on Aug 11, 2017

   Owner

   More actions

   strange, i have the same node / npm versions as you and it worked on a clean clone for me. try removing your node_modules folder and using yarn install instead of npm install.
2. coryhouse commented on Aug 12, 2017

   

   coryhouse

   on Aug 12, 2017

   Author

   More actions

   I've tried both npm and yarn. Deleted node_modules before each try. Stumped.
3. MilanPavel commented on Sep 6, 2017

   

   MilanPavel

   on Sep 6, 2017

   More actions

   I have the same issue, tried with both npm and yarn install. Any idea? (MacOS, Node 7.0.4, npm 4.0.5)
4. MilanPavel commented on Sep 7, 2017

   

   MilanPavel

   on Sep 7, 2017

   More actions

   There seems to be some problem with localhost on my Mac. As a workaround when using 127.0.0.1 in URL instead localhost and also updating webpack.config.js it works.

   change in webpack.config.js:
   output: {
   publicPath: 'http://127.0.0.1:8080/'
5. andrewngu commented on Sep 7, 2017

   

   andrewngu

   on Sep 7, 2017

   Owner

   More actions

   Ah, that makes sense. Perhaps it's an mac osx setting that prevents binds on 0.0.0.0, which I used to test on a mobile device. Thanks for figuring it out.