Skip to content

Devtools steps into ignored files and makes debugging very annoying #896

Open
@ohjah

Description

@ohjah

The image speaks for itself.

Detours into third-party files really distract from the debugging process. That’s why Chrome DevTools includes an "Ignore List" feature—but for some reason, it doesn’t seem to be doing what it's supposed to.

Everyone is always saying, "Don’t use console.log to debug." But when tools like this don’t behave as expected, it’s no wonder so many JavaScript developers never truly learn how to debug effectively.

In addition to that (could be an Expo/Metro-related thing), the files in the left pane are never shown in any kind of folder structure—they’re just listed one after another, with long and unreadable paths like this:
http://192.168.0.206:8081/workspaces/clients/app/src/index.ts.bundle//C:\Users\user\Develop\app\node_modules\@babel\runtime\helpers\objectDestructuringEmpty.js (from source map) (ignore listed)

Image

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions