New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 763639 link

Starred by 4 users

Issue metadata

Status: WontFix
Owner:
Last visit 28 days ago
Closed: Dec 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Webpack source code mappings not detected

Reported by mike.tal...@3radical.com, Sep 9 2017

Issue description

DevTools failed to link network resource to filesystem.

Platform: Mac
Chrome version: 63.0.3210.0
Webpack 3.5.5

In main line Chrome I can link source fine, but in Canary this has stopped working. In Canary nothing is linked at all and it keeps letting me add a local folder but doesn't then perform any mapping.  As I can only add a mapping on a source file I can't "tell it" where the root of the project is - not sure if this is relevant.

Screenshots from Canary and one from Chrome that shows it working previously.

Project is on PlayCanvas: https://playcanvas.com/project/503148/overview/alphabet-frame-viewer

But the webpack source is presently closed.
 
Screen Shot 2017-09-09 at 09.15.37.png
696 KB View Download
Screen Shot 2017-09-09 at 09.15.55.png
94.8 KB View Download
Screen Shot 2017-09-09 at 09.17.14.png
511 KB View Download
Screen Shot 2017-09-09 at 09.18.24.png
694 KB View Download
Just to point out, I've tried adding all of the different source folders, the effect is the same.

Further comment lol.  Webpack sourcemap mode of inline-source-map
Cc: jmukthavaram@chromium.org
Labels: Needs-Feedback Needs-Triage-M63
Thanks for filing the issue.
Could you please check the same issue on latest Canary#63.0.3212.0.If still issue observed, please provide us clear steps,OS & expected result to reproduce the issue from our end.

Owner: kozyatinskiy@chromium.org
Status: Assigned (was: Unconfirmed)
Cc: kozyatinskiy@chromium.org
Owner: lushnikov@chromium.org
Looks like persistent issue, Andrey, please take a look.
I am under the same conditions of OP and I can confirm this is happening also for me on Canary 63.0.3233.0 and Mac Os 10.11.6

I can see sourcemaps for sass files but not those of Js/JSX files.

This used to work until few days ago for me.
Same issue, started happening with a recent canary release just like comment 6.
Status: WontFix (was: Assigned)
Hi everybody,

We recently introduced the "Persistence 2.0" - workspaces that establish mappings automatically. One of the conditions for this to happen is that content of both file and loaded resource exactly match.

In case of webpack, we've seen a lot of loaders that were fiddling with sourcemap files and didn't fill in proper content. This would make the automapping not work (which is actually reasonable since there's no way to map to non-equal resources).

Speculatively closing this since it looks very much like this case.

Sign in to add a comment