Juan 6abda7f4f2 [DevTools] Access metadata in source maps correctly accounting for different formats (#22096) ...

## Summary

Follow up from https://github.com/facebook/react/pull/22010.

The initial implementation of named hooks and for looking up hook name metadata in an extended source map both assumed that the source maps would always have a `sources` field available, and didn't account for the source maps in the [Index Map](https://sourcemaps.info/spec.html#h.535es3xeprgt) format, which contain a list of `sections` and don't have the `source` field available directly. 

In order to properly access metadata in extended source maps, this commit:

-  Adds a new `SourceMapMetadataConsumer` api, which is a fork / very similar in structure to the corresponding [consumer in Metro](2b44ec39b4/packages/metro-symbolicate/src/SourceMetadataMapConsumer.js (L56)) (as specified by @motiz88 in https://github.com/facebook/react/issues/21782.
- Updates `parseHookNames` to use this new api

## Test Plan

- yarn flow
- yarn test
- yarn test-build-devtools
- added new regression tests covering the index map format
- named hooks still work on manual test of browser extension on a few different apps (code sandbox, create-react-app, internally).

2021-08-18 14:30:31 -04:00

..

index.js

make parseHookNames a separate bundle (#22102)

2021-08-16 16:46:46 -04:00

parseHookNames.js

[DevTools] Access metadata in source maps correctly accounting for different formats (#22096)

2021-08-18 14:30:31 -04:00

parseHookNames.worker.js

[DRAFT] Import scheduling profiler into DevTools Profiler (#21897)

2021-07-22 13:58:57 -04:00