Searched refs:traces (Results 1 – 17 of 17) sorted by relevance
| /expo/packages/@expo/config/src/ |
| H A D | evalConfig.ts | 74 const traces = error.stack?.split('\n').filter((line) => !line.startsWith(' at ')); constant 75 if (!traces) return null; 78 if (traces[traces.length - 1].startsWith('SyntaxError:')) { 79 traces.pop(); 81 return traces.join('\n');
|
| /expo/packages/@expo/config/build/ |
| H A D | evalConfig.js | 108 …const traces = (_error$stack = error.stack) === null || _error$stack === void 0 ? void 0 : _error$… 109 if (!traces) return null; 112 if (traces[traces.length - 1].startsWith('SyntaxError:')) { 113 traces.pop(); 115 return traces.join('\n');
|
| H A D | evalConfig.js.map | 1 …traces","stack","split","filter","startsWith","length","pop","join","SyntaxError","constructor","n…
|
| /expo/packages/@expo/metro-runtime/src/error-overlay/ |
| H A D | index.tsx | 17 // Stack traces are big with React Navigation
|
| /expo/docs/pages/debugging/ |
| H A D | errors-and-warnings.mdx | 3 description: Learn about Redbox errors and stack traces in your Expo project. 20 ## Stack traces 32 ….js**. This is a typical example of how helpful error messages and stack traces can be if you take…
|
| H A D | runtime-issues.mdx | 24 …is by looking at the [stack trace](/debugging/errors-and-warnings/#stack-traces). However, in some…
|
| /expo/packages/@expo/metro-runtime/build/error-overlay/modules/parseErrorStack/ |
| H A D | index.js.map | 1 … this.\n // // Native support for parsing for non-standard Hermes stack traces.\n // if (global.…
|
| /expo/packages/@expo/metro-runtime/build/error-overlay/ |
| H A D | index.js.map | 1 …E_ENV === 'development') {\n if (Platform.OS === 'web') {\n // Stack traces are big with React…
|
| /expo/packages/expo-router/src/ |
| H A D | renderRootComponent.tsx | 78 // Console is pretty useless on native, on web you get interactive stack traces.
|
| /expo/packages/expo-yarn-workspaces/ |
| H A D | CHANGELOG.md | 103 …ig` with deprecated `.expo.*` extension support and improved error stack traces. ([#12252](https:/…
|
| /expo/packages/expo-router/build/ |
| H A D | renderRootComponent.js.map | 1 …// Console is pretty useless on native, on web you get interactive stack traces.\n if (Platform…
|
| /expo/packages/@expo/metro-config/build/ |
| H A D | customizeFrame.js.map | 1 …n\n/**\n * The default frame processor. This is used to modify the stack traces.\n * This method a…
|
| /expo/packages/@expo/metro-config/ |
| H A D | CHANGELOG.md | 173 - Ignore `react-dom` traces. ([#21005](https://github.com/expo/expo/pull/21005) by [@EvanBacon](htt…
|
| /expo/packages/@expo/config-plugins/build/plugins/ |
| H A D | createBaseMod.js.map | 1 …erate the function name to ensure it's uniform and also to improve stack traces.\n const methodNa…
|
| /expo/packages/expo-updates/ |
| H A D | CHANGELOG.md | 757 …ig` with deprecated `.expo.*` extension support and improved error stack traces. ([#12252](https:/…
|
| /expo/packages/expo-dev-launcher/ios/ |
| H A D | main.jsbundle | 224 …n.height>=0}))))}),(function(t){console.error(`Failed to measure updated traces. Error: ${t}`)}))}… 846 …pt --code-comments --hydrogen-track-positions --redirect-code-traces --redirect-code-traces-to=cod…
|
| /expo/packages/expo-dev-launcher/android/src/debug/assets/ |
| H A D | expo_dev_launcher_android.bundle | 222 …n.height>=0}))))}),(function(t){console.error(`Failed to measure updated traces. Error: ${t}`)}))}… 847 …pt --code-comments --hydrogen-track-positions --redirect-code-traces --redirect-code-traces-to=cod…
|