Inaccurate stacktraces and can't debug from source files when using TS or other transpiled languages

[ScottPierce]

Description

I am not able to get proper stacktraces from dev or properly debug the from my source files because sourcemaps for .js files seem to be ignored in dev.

React Native version:

npx react-native info
info Fetching system and libraries information...
System:
 OS: macOS 10.15.4
 CPU: (12) x64 Intel(R) Core(TM) i9-8950HK CPU @ 2.90GHz
 Memory: 136.93 MB / 32.00 GB
 Shell: 3.2.57 - /bin/bash
 Binaries:
 Node: 14.1.0 - /usr/local/bin/node
 Yarn: 1.10.1 - /usr/local/bin/yarn
 npm: 6.14.4 - /usr/local/bin/npm
 Watchman: 4.9.0 - /usr/local/bin/watchman
 Managers:
 CocoaPods: 1.9.1 - /usr/local/bin/pod
 SDKs:
 iOS SDK:
 Platforms: iOS 13.4, DriverKit 19.0, macOS 10.15, tvOS 13.4, watchOS 6.2
 Android SDK:
 API Levels: 26, 27, 28, 29
 Build Tools: 26.0.2, 27.0.3, 28.0.3, 29.0.1, 29.0.2
 System Images: android-23 | Google APIs Intel x86 Atom_64, android-28 | Google APIs Intel x86 Atom, android-28 | Google Play Intel x86 Atom, android-29 | Google Play Intel x86 Atom
 Android NDK: Not Found
 IDEs:
 Android Studio: 3.6 AI-192.7142.36.36.6392135
 Xcode: 11.4.1/11E503a - /usr/bin/xcodebuild
 Languages:
 Java: 1.8.0_211 - /usr/bin/javac
 Python: 2.7.17 - /usr/local/bin/python
 npmPackages:
 @react-native-community/cli: Not Found
 react: 16.11.0 => 16.11.0 
 react-native: 0.62.2 => 0.62.2 
 npmGlobalPackages:
 *react-native*: Not Found

Steps To Reproduce

Provide a detailed list of steps that reproduce the issue.

1. Run the provided project
2. See the following crash:
   

Expected Results

The stack trace and debugging aren't taking advantage of the provided source-maps for the files in ./lib at all. I should get a stack trace that references the .kt source files, and I should also be able to debug/breakpoint from the .kt source files when I attach them in chrome.

Snack, code example, screenshot, or link to a repository:

https://www.dropbox.com/s/ufj75r59yslfvjd/react-native-sourcemap-error.zip?dl=0

[stale]

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may also label this issue as a "Discussion" or add it to the "Backlog" and I will leave it open. Thank you for your contributions.

[ScottPierce]

This issue hasn't been fixed, and yes, it needs to be.

[stale]

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may also label this issue as a "Discussion" or add it to the "Backlog" and I will leave it open. Thank you for your contributions.

[ScottPierce]

This issue hasn't been fixed, and yes, it needs to be.

[github-actions]

This issue is stale because it has been open 180 days with no activity. Remove stale label or comment or this will be closed in 7 days.

[github-actions]

This issue was closed because it has been stalled for 7 days with no activity.