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

Issue 594085 link

Starred by 3 users

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: Apr 2016
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Source map not work when ' webpack -d --progress --colors --watch'

Reported by qcgm197...@gmail.com, Mar 11 2016

Issue description

<b>Chrome Version       : <Copy from: 'about:version'></b>51.0.2673.0
URLs (if applicable) :
Other browsers tested:Ok Chrome Version 47.0.2526.111 (64-bit) for mac
  Add OK or FAIL, along with the version, after other browsers where you
have tested this issue:
     Safari:Not support all along
    Firefox:45.0a2 Ok
         IE:Not test

What steps will reproduce the problem?
(1)Excute 'webpack -d --progress --colors --watch'
(2)Open index.html refs bundle.js


What is the expected result?
bundle.js can map the relevant jsx file 

What happens instead?
Console: 'Failed to parse SourceMap: http://localhost:63343/AuthoringTool/build/bundle.js.map' 

Please provide any additional information below. Attach a screenshot if
possible.
Today I update Canary and the problem occurs

 
Hi can you please provide the index.html refs bundle.j page ,so we can debug this issue and update.Thanks
Labels: Needs-Feedback
@mmohammad@chromium.org Today the problem is not reproduced, maybe it's my code error.
Thank you.
Project Member

Comment 4 by sheriffbot@chromium.org, Mar 16 2016

Labels: -Needs-Feedback Needs-Review
Owner: mmohammad@chromium.org
Status: Assigned (was: Unconfirmed)
Thank you for providing more feedback. Assigning to requester "mmohammad@chromium.org" for another review.

For more details visit https://sites.google.com/a/chromium.org/dev/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 5 by ratsu...@gmail.com, Mar 17 2016

Hi everyone, I still ran into this issue, my chorme version is 51.0.2680.0 canary (64-bit), on Mac OS X.

And...sorry I cannot provide the js file and map file, they are too large and I cannot create a simple example to reproduce this issue.

Just let you know the issue is still exist, may related with webpack and it works one or two weeks before. Thanks
@ratsu...@gmail.com I meet the problem again...
I found only execute webpack and the browser parse is successfully, but if I add the --watch option the parse would fail.  
The chromium Version 51.0.2680.0 (64-bit) works correctly. The only failed browser is Canary
The error disappeared again after I modified some arbitrary code...

Comment 10 by ratsu...@gmail.com, Mar 18 2016

Hi @qcgm197874, could you upload your .js, .map file to here? Maybe it can help resolve the problem.

@mmohammad, I believe this issue is a chromium side issue because I doesn't see error message on chrome stable version 49.0.2623.87 (64-bit) for same map file, could you provide any help? Thanks~
Status: WontFix (was: Assigned)
Closing as per #9. Please reopen if needed.

Sign in to add a comment