@ChromeDevTools Why does the mapping feature never work for me? Every few months I try it, and it always fails to associate the source map with a file no matter what I do. Reproducing case: any Create React App project.pic.twitter.com/bPpej3JVKA
Somebody on the team looked into it previously. They're checking it out again. --- @kaycebasques
-
-
The official response from
@aslushnikov was "This is a known issue with webpack; we can't do much" because "Webpack changes the content of the sourcemaps resources". This was a side effect of the Workspaces 2 Chrome feature. More info: https://github.com/webpack/webpack/issues/2145#issuecomment-350054778 … cc@TheLarkInn -
- Workspace mapping not working in 63 https://bugs.chromium.org/p/chromium/issues/detail?id=796251 … - Sourcemaps need to be identical to the ones on the file system, "This seems to be bothering a lot of people" https://bugs.chromium.org/p/chromium/issues/detail?id=797486 … - After Chrome Update my javascript files aren't mapped https://bugs.chromium.org/p/chromium/issues/detail?id=793241 …
- 1 more reply
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.