Joshua Gross 308d63fe93 console.log shouldn't throw warning if metro isn't running ...

Summary: When metro is not running, D15559151 caused infinite exceptions (fetch threw an error if it couldn't connect to localhost:8081) which affected UI. Swallow those errors and everything works well, with or without metro.

Reviewed By: yungsters

Differential Revision: D15588623

fbshipit-source-id: d170ea82478545836a7a22a228196c9778e93ef0

2019-05-31 17:08:19 -07:00

..

__tests__

Migrate "Libraries" from Haste to standard path-based requires (sans vendor & renderers) (#24749)

2019-05-08 08:48:59 -07:00

getDevServer.js

Add spec for SourceCode (#24901)

2019-05-22 03:27:54 -07:00

logToConsole.js

console.log shouldn't throw warning if metro isn't running

2019-05-31 17:08:19 -07:00

openFileInEditor.js

Migrate "Libraries" from Haste to standard path-based requires (sans vendor & renderers) (#24749)

2019-05-08 08:48:59 -07:00

openURLInBrowser.js

Open links from new app screen in computer's browser (#24843)

2019-05-14 07:07:24 -07:00

parseErrorStack.js

Add spec for ExceptionsManager (#24900)

2019-05-22 13:10:24 -07:00

setupDevtools.js

Migrate "Libraries" from Haste to standard path-based requires (sans vendor & renderers) (#24749)

2019-05-08 08:48:59 -07:00

symbolicateStackTrace.js

Add spec for ExceptionsManager (#24900)

2019-05-22 13:10:24 -07:00