Moti Zilberman 4c911a2dec Filter out Hermes internal bytecode frames from error stack traces ... Summary: Changelog: [Fixed][General] Filter out Hermes internal bytecode frames (Promise implementation) from error stack traces Currently, React Native strips native frames from call stacks reported via ExceptionsManager / LogBox. This diff does the same for *internal bytecode* frames in Hermes, which are functionally similar to native frames: they are implementation details of the engine for which source code isn't readily available. In particular this change will avoid confusing symbolication tools that may otherwise try to treat `InternalBytecode.js` frames as belonging to the main React Native bundle (and produce garbage output). Reviewed By: GijsWeterings Differential Revision: D42367135 fbshipit-source-id: b7904f10c7ff6956e7b736b575dde1ce45028200		2023-01-05 11:05:39 -08:00
..
__tests__	Filter out Hermes internal bytecode frames from error stack traces	2023-01-05 11:05:39 -08:00
getDevServer.js	Update copyright headers from Facebook to Meta	2021-12-30 15:11:21 -08:00
openFileInEditor.js	chore: add headers.Content-type to openFileInEditor call (#33517)	2022-10-03 10:32:29 -07:00
openURLInBrowser.js	Update copyright headers from Facebook to Meta	2021-12-30 15:11:21 -08:00
parseErrorStack.js	Filter out Hermes internal bytecode frames from error stack traces	2023-01-05 11:05:39 -08:00
parseHermesStack.js	Filter out Hermes internal bytecode frames from error stack traces	2023-01-05 11:05:39 -08:00
symbolicateStackTrace.js	RN: Sort Imports via ESLint	2022-09-30 14:28:48 -07:00