Dan Abramov ea817fd7f5 Don't symbolicate transform errors ...

Summary:
Metro symbolication can be expensive in large apps. However, there is no need to symbolicate _runtime stacks from compile errors_. Those are pretty much useless anyway.

This will reduce the workload on Metro workers, and the delays when iterating with Fast Refresh, as the server will be busy much less often.

So I'm special-casing them and not sending the symbolication request anymore.

Reviewed By: rickhanlonii

Differential Revision: D16030087

fbshipit-source-id: 41f83ac01780c0a60cca777014e4ed95c0f3d14b

2019-06-27 07:58:50 -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

Don't symbolicate transform errors

2019-06-27 07:58:50 -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