Skip to content

Bug: RDT commonly fails to find source #34581

@doggybootsy

Description

@doggybootsy

When using RDT it commonly fails to open to find the source of a functional component. In my testing the functional component must have a hook to find its source.

I'm guessing if RDT would switch back to using something like what happened before this commit e528728#diff-1237c8d5ba2b9883dbe73805ad8bebd84cb20ae1aec03855e545a4be0b0684f9 would fix this problem. It could use $r.type instead of $type

React Version: 19.1.1
React Devtools version: 6.1.5

Steps To Reproduce

1.Open RDT
2.Try to view source of a function component without a hook

Link to code example:

Example of this happening is on https://nlkwvr.csb.app/

The current behavior

Button is disabled when functional component has no hooks

The expected behavior

Button to not be disabled and just work

Metadata

Metadata

Assignees

No one assigned

    Labels

    Status: UnconfirmedA potential issue that we haven't yet confirmed as a bug

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions