Debugger Steps Through Ignored Files

[3flippa]

Description

I'm trying to use the Sources tab in DevTools to efficiently debug my application. Unfortunately, the debugger is stepping through not only the files I've authored but also files inside the node_modules directory—even ones I've configured to be ignored.

This significantly degrades the development experience, as it clutters the debugging flow and makes it hard to focus on the logic relevant to my own code.

Steps to reproduce

1. create a simple expo or rn project
2. use sources tab to debug

React Native Version

0.79.2

Output of npx @react-native-community/cli info

info Fetching system and libraries information...
System:
  OS: Windows 11 10.0.26100
  CPU: (16) x64 AMD Ryzen 7 PRO 4750U with Radeon Graphics   
  Memory: 3.09 GB / 15.23 GB
Binaries:
  Node:
    version: 20.18.3
    path: C:\Program Files\nodejs\node.EXE
  Yarn: Not Found
  npm:
    version: 10.8.2
    path: C:\Program Files\nodejs\npm.CMD
  Watchman: Not Found
SDKs:
  Android SDK: Not Found
  Windows SDK: Not Found
IDEs:
  Android Studio: AI-242.23339.11.2421.12550806
  Visual Studio: Not Found
Languages:
  Java: Not Found
  Ruby: Not Found
npmPackages:
  "@react-native-community/cli": Not Found
  react: Not Found
  react-native: Not Found
  react-native-windows: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: Not found
  newArchEnabled: Not found
iOS:
  hermesEnabled: Not found
  newArchEnabled: Not found

Screenshots and Videos

[react-native-bot]

Warning

Missing reproducer: We could not detect a reproducible example in your issue report. Reproducers are mandatory and we can accept only one of those as a valid reproducer:

• For majority of bugs: send us a Pull Request with the RNTesterPlayground.js edited to reproduce your bug.
• If your bug is UI related: a Snack
• If your bug is build/upgrade related: a project using our Reproducer Template

You can read more about about it on our website: How to report a bug.

[3flippa]

i honestly think because of the basic nature of the bug there is no need for a reproducer template

[cipolleschi]

Hi @3flippa thanks for the issue. We realized that we fixed the issue in a few commits that landed in Hermes after we released 0.79.
We already have the fix ready and it will be shipped in 0.79.3.

[AndreiDIT98]

@cipolleschi

Is there really no fix or workaround planned for those who, for any reason, are not ready to migrate to version 0.79.3? For instance, I am still actively developing and maintaining apps that rely on 0.76.2.

At the moment, debugging with DevTools and breakpoints is almost unusable, especially when dealing with async/await functions. The debugger will wildly jump into a lot of foreign/3rd party files.

[3flippa]

@cipolleschi
most perfect resopnse i ever got haha. thank u very much.
do u know when this version will be shipped?