Skip to content

Source maps for css/sass #2020

Closed
Closed
@retallicka

Description

@retallicka

I am using the following setup:

Mac OSX El capitan
angular-cli v1.0.0-beta.11-webpack.8, branch: master
node 6.5.0
os: darwin x64
Using Sass

This might not be a bug with angular-cli, perhaps it is a limitation with angular2 but I am looking for anyone who's managed to solve this. I cannot get the sass to be source mapped. I want to inspect the CSS and see where a particular value is being set.

Personally, I am trying to work out how to edit the setup so I can do this locally. I am not too concerned in editing the webpack config, this is only going to be an issue in development, not production. But thinking globally, I think this should just work for anyone using angular-cli.

I have tried adding the source map commands here to webpack-build-common but no luck... I still see only the css in the head and nothing external.

I also saw another user trying something here with LESS, maybe I can do similar...
#1656 (comment)

I also found this issue in the angular project but it appears to be fixed now.

This issue appears whether I use css, sass and whether I change ViewEncapsulation within the component or not.

I am not at all familiar with webpack and only angular 1.5 so please forgive me. Any help appreciated :)

Edit: here is my project setup

Metadata

Metadata

Assignees

Labels

P3An issue that is relevant to core functions, but does not impede progress. Important, but not urgentneeds: investigationRequires some digging to determine if action is neededtype: bug/fix

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions