evanw/node-source-map-support

Support absolute file:// paths in sourceMappingURL

Open

#133 建立於 2016年4月27日

在 GitHub 查看
 (6 留言) (2 反應) (0 負責人)JavaScript (2,078 star) (242 fork)batch import
help wanted

描述

Hi! I'm working on https://github.com/mozilla/tofino and we have some interesting requirements. It appears that we need absolute file:// paths in our sourceMappingURL to support source maps in the (Chrome) devtools that Electron provides natively. That is, we want:

//# sourceMappingURL=file:///Users/nalexander/Mozilla/tofino/lib/main/browser.map

Unfortunately, that conflicts with source-map-support, which doesn't appreciate absolute paths of this kind. Would you merge a patch to handle (in Node.js only) file:// protocols?

貢獻者指南

技術棧
javascriptnodejs
領域
backendtooling
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
half day
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
Basic Node.js path handlingUnderstanding of source maps
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
60
研究方向
Investigate the source map support library's URL resolution logic, particularly how it parses `sourceMappingURL` in stack traces. The relevant file is likely `lib/source map support.js`. Look for where the URL is converted to a file path. The issue requests support for absolute `file://` paths. Consider stripping the `file://` protocol and using the path as is on Unix, but note that Windows paths like `file:///C:/...` may need special handling. Review existing comments (there are 6) for any additional context or attempted solutions. A new contributor could implement a patch that detects `file://` and extracts the absolute path, then tests it locally.