Amjad Masad 734edf5cd4 [react-packager] Socket Server should not die while there active connections ...

Summary:
Saw an issue with a build because of an ENONT error: https://fb.facebook.com/groups/716936458354972/permalink/923628747685741/

My hypothesis:

1. We issue a ping to the socket (in SocketInterface/index.js) a decides if the available socket is alive
2. We see that it's alive but by the time we actually connect to it the server would've died

Solution:

1. The server shouldn't die as long as there are clients connected to it (currently it only stay alive as long as there are jobs)
2. The "ping" should only disconnect once the client is connected
3. Finally, have a better error message than ENOENT

2015-09-03 14:48:19 -08:00

..

__mocks__

[react-packager] Expose a socket interface

2015-08-25 09:37:08 -08:00

src

[react-packager] Socket Server should not die while there active connections

2015-09-03 14:48:19 -08:00

.babelrc

[Babel] Upgrade babel and regenerator to the latest version

2015-08-10 20:37:39 -08:00

.npmignore

[react-packager][streamline oss] Move open sourced JS source to react-native-github

2015-02-19 21:25:11 -08:00

index.js

[react-packager] Cleanup socket interface code

2015-08-25 17:36:08 -08:00