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

Issue 801223 link

Starred by 5 users

Issue metadata

Status: Archived
Owner:
Last visit 28 days ago
Closed: Dec 8
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Workspaces 2.0 broken source mapping

Reported by came...@remitly.com, Jan 11 2018

Issue description

DevTools failed to link network resource to filesystem.

Platform: macOS 10.13.2 (17C88)
Chrome version: 63.0.3239.132 (Official Build) (64-bit)

What are the details of your project?
- Build System: webpack
- HTTP server: webpack dev server

Assets failed to link (or incorrectly linked):
all in project, here's an example
The local file "file:///Users/cameronlittle/Dev/narwhal/src/components/addressForm/disableSelfAutofill.tsx" should be mapped to "http://localhost:3000/src/components/addressForm/disableSelfAutofill.tsx"

Also, the dev tools are still prompting me to manually establish a mapping, which doesn't work

If possible, please attach a screenshot of network sources navigator which should
show which resources failed to map

 
Screen Shot 2018-01-11 at 09.43.30.png
26.4 KB View Download
Screen Shot 2018-01-11 at 09.45.51.png
46.3 KB View Download

Comment 1 by came...@remitly.com, Jan 11 2018

This was previously working before chrome 63 (https://developers.google.com/web/updates/2017/10/devtools-release-notes#workspaces)
Owner: lushnikov@chromium.org
Status: Assigned (was: Unconfirmed)

Comment 3 by elmo...@gmail.com, Feb 2 2018

I am experiencing the same issue with Windows 10 64-bit. Very frustrating.

Chrome Version 64.0.3282.140 (Official Build) (64-bit)
Status: Archived (was: Assigned)
Workspaces 2.0 is imperfect and there's no feasible way to make it work for everybody. Archiving since we currently don't have resources to allocate towards improving Workspaces story.


Sign in to add a comment