https://github.com/symind/browser-sourcemap-spy

Analyze how browsers fetch source maps in real-time.
https://github.com/symind/browser-sourcemap-spy

Last synced: 26 days ago
JSON representation

Analyze how browsers fetch source maps in real-time.

• Host: GitHub
• URL: https://github.com/symind/browser-sourcemap-spy
• Owner: SyMind
• License: mit
• Created: 2024-02-01T09:41:23.000Z (9 months ago)
• Default Branch: main
• Last Pushed: 2024-02-04T09:33:33.000Z (9 months ago)
• Last Synced: 2024-02-04T10:23:18.346Z (9 months ago)
• Language: JavaScript
• Size: 10.7 KB
• Stars: 0
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# browser-sourcemap-spy

Analyze how browsers fetch source maps in real-time.

# The `SourceMap` or `X-SourceMap` HTTP Header

The SourceMap or X-SourceMap HTTP header is an integral response header that is primarily utilized in JavaScript (JS) files. Its main function is to create a linkage between the original source code and the resulting compiled code. Within a JS file, this connection is facilitated by the inclusion of a reference tag, such as `//# sourceMappingURL`, which points to the source map's location. 

# Reason for Absence of Sourcemaps in Network Tab

As discussed in the Chromium bug tracker https://bugs.chromium.org/p/chromium/issues/detail?id=362913, sourcemaps are not considered standard page resources.

The intention behind the Network tab is to display resources that are a part of an ordinary page load, reflecting the actual network activity. Sourcemaps, while useful for debugging, do not fall under the category of typical resource loads as they're utilized primarily for development purposes.

In essence, this means there is no option within Chrome to force sourcemaps to appear in the Network tab due to their categorization outside the scope of normal web page resource loading events.