The ignored frames are grayed out when expanded. The image shows the stack traces before and after you expand the stack trace in the Console.

Chrome DevTools will apply this information to hide frames from those ignored files. Given that the two files node_modules/…/frameworks.js and node_modules/./library.js are third party scripts, you can specify the x_google_ignoreList field to indicate their positions in the sources field. Watch What are source maps? to learn how the mappings work. The sources field shows a list of original sources used by the mappings entry.

For example, let’s look at the following source map. Such fields are prefixed with x_.Ĭhrome DevTools uses the x_google_ignoreList field (if provided), to filter out generated code and let web developers focus only on the code they author. Source maps extensions are additional fields that store complementary information about the source map. The later hides away irrelevant third-party frames to help you pinpoint issues quicker during debugging. The image shows the stack traces before and after Chrome DevTools supports x_google_ignoreList. DevTools automatically hides all the third party frames, and shows only the frames that are relevant to your code. Take a look at the following stack trace in the Console. Chrome DevTools parses the x_google_ignoreList field in source maps to help improve developer debugging experience.

Keepass google chrome extension