DevTools named hook parsing logic currently matches AST nodes using the original line number:
https://github.com/facebook/react/blob/ed6c091fe961a3b95e956ebcefe8f152177b1fb7/packages/react-devtools-extensions/src/parseHookNames.js#L341-L346
But this may not be sufficient, as mentioned in comment #21641 (comment):
Are we assuming that a line number is sufficient to identify a hook call? Seems like that assumption breaks down in edge cases:
- Minified code (either without a source map, or a bundle built from pre-minified inputs) can have multiple hooks on one line.
- Some code might be authored with quirky formatting, i.e. not with a typical Prettier / ESLint setup.
DevTools named hook parsing logic currently matches AST nodes using the original line number:
https://github.com/facebook/react/blob/ed6c091fe961a3b95e956ebcefe8f152177b1fb7/packages/react-devtools-extensions/src/parseHookNames.js#L341-L346
But this may not be sufficient, as mentioned in comment #21641 (comment):