css file mapping only works when map contains sourcesContent
Reported by
marcelva...@gmail.com,
Jan 24 2018
|
||||
Issue descriptionDevTools failed to link network resource to filesystem. Platform: <Win> Chrome version: Version 63.0.3239.132 (Official Build) (64-bit) Chrome canary version: Version 66.0.3329.1 (Official Build) canary (64-bit) What are the details of your project? - Build System: node-sass - HTTP server: ng serve Assets failed to link (or incorrectly linked): Source maps generated by node-sass without the flag --source-map-contents aren't linked at all (devtools sources shows empty tab) Source maps generated like this are linked properly: node-sass --source-maps true --source-map-contents Apparently chrome needs maps with sourcesContent. The file is found based on the content. I'd expect an error message like: 'chrome cant link network resource to filesystem because map doesn't contain sourcesContent'. Tt would be nice if the option to "map to local file" returned when chrome fails to find the file.
,
Jan 31 2018
@lushnikov: Could you please confirm whether this issue is similar to that of 796368, 794965 and 796251. Thanks!
,
Jan 31 2018
,
Feb 1 2018
Difference with issues 796368 , 794965 and 796251 is that they don't know why resources weren't linked. I know my resource weren't linked because my maps didn't contain sourcesContent. So I'm asking for an alert when maps don't contain sourcesContent, so I know what to do to enable automated mapping. I was also suggesting the "map to local file" option be returned whenever resources weren't found. Maybe this could be a separate (more general) issue.
,
Apr 5 2018
I'm the poster of 812681. Getting the sourcemap contents did let my scss file map, but the css file and doesn't. Which means any changes I make to the scss file gets saved to my local machine, sass recompiles, and then nothing... Chrome never changes the displayed styling as its still using the remote css file and not my local one. Because it never got mapped.
,
Dec 8
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 |
||||
Comment 1 by krajshree@chromium.org
, Jan 30 2018