@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
-
@ChromeDevTools Surely you can collaborate with#Webpack contribs like@wSokra or@TheLarkInn to remedy this. Perhaps make The `Workspaces 2.0` feature optional. In a world of transpiling and packing, enforcing this seems like a step backwards.
Hey @jake_niemiec, Workspaces 2.0 *is* opt-in, not sure I understand what you mean by "make it optional". And thanks for providing the extra context with links and whatnot 
--- @kaycebasques
-
-
Wonderful! Can you tell me how to opt out and go back to explicitly mapping my files?
I looked in Preferences, Workspace, Experiments (even the secret SHIFT ones) and chrome://flags. You use to be able to disable it via `Persistence 2.0` Experiment.pic.twitter.com/zd4PIIxuMl
-
Ah, I see. Yeah, at the moment the explicit mappings are gone from Workspaces 2. I'm hearing a lot of feedback similar to yours, though, and we're exploring our options --- kayce
- 2 more replies
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.