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

Issue 621685 link

Starred by 3 users

Issue metadata

Status: WontFix
Owner:
Last visit 29 days ago
Closed: Jul 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

Source Map not mapping correctly

Reported by jason.ts...@bloomreach.com, Jun 20 2016

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36

Steps to reproduce the problem:
1. Using react with webpack dev server
2. Using "#source-map" for devtool config

What is the expected behavior?
The mapping shown in source inspector should match the actual file content

What went wrong?
The source file tree is shown but mapping for files to contents are off, which wasn't the case prior to upgrading to v.51

Did this work before? Yes v49 (possibly v50)

Chrome version: 51.0.2704.103  Channel: stable
OS Version: OS X 10.10.5
Flash Version: Shockwave Flash 22.0 r0
 
Cc: kozyatinskiy@chromium.org
I believe there's a thread about this on the webpack issue tracker. Can you look that up?  We're going to need a small demo app to test before we can look into if its our regression.
Labels: Needs-Feedback

Comment 3 by alph@chromium.org, Jul 15 2016

Owner: lushnikov@chromium.org
Status: WontFix (was: Unconfirmed)
Won't fix due to lack of feedback

Sign in to add a comment