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

Issue 799431 link

Starred by 1 user
Status: Archived
Owner:
█ lushnikov@chromium.org
Last visit 28 days ago
Closed: Dec 12
Cc:
█ sc00335...@techmahindra.com
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Errors point to files from a totally different project

Reported by grahamfo...@gmail.com, Jan 5 2018 
UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.132 Safari/537.36

Steps to reproduce the problem:
1. Open developer tool console tab
2. Make your code produce an error
3. check the stack, errors point to a files in a totally different project

What is the expected behavior?
the stack trace should point to files in the current project

What went wrong?
I have multiple angular 4 projects on my system, running them using Angular CLI.  in the sources section of dev tools i have webpack://path/to/different/project.  for some reason all errors seem to point to files in this other project.

Did this work before? Yes unknown - found on version 63.0.3239.132

Chrome version: 63.0.3239.132  Channel: stable
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version:
wrong-source.png
89.1 KB View Download

Comment 1 by sc00335...@techmahindra.com, Jan 8 2018

Cc: sc00335...@techmahindra.com
Labels: Needs-Feedback Needs-Triage-M63
grahamfowles@ Thanks for the issue.

Can you please provide sample test file to reproduce this issue, which will help in further triaging.

Thanks...

Comment 2 by eostroukhov@chromium.org, Jan 8 2018

Owner: lushnikov@chromium.org
Status: Assigned (was: Unconfirmed)

Comment 3 by lushnikov@chromium.org, Dec 12

Status: Archived (was: Assigned)
►

Sign in to add a comment