Skip to content
This repository has been archived by the owner on Aug 4, 2021. It is now read-only.

SCSS maps #21

Open
Tenemo opened this issue Sep 17, 2017 · 2 comments
Open

SCSS maps #21

Tenemo opened this issue Sep 17, 2017 · 2 comments
Labels
2.1.0 bug

Comments

@Tenemo
Copy link

Tenemo commented Sep 17, 2017 •
edited
Loading

Is there any way to map the SCSS files so I can see what file produced given CSS rule? Except for global styles, which are excluded from the rule and compiled to the styles file, every component SCSS gets dumped into the tag. Is it possible to avoid that, so Chrome Dev Tools would be able to tell where the rules originate from?
@Tynarus
Copy link
Owner

Tynarus commented Sep 18, 2017

Of course! I'll look into getting those sourcemaps back in there!

@Tynarus
Copy link
Owner

Tynarus commented Sep 27, 2017

@Tenemo Seems this has to do with an Angular bug as well... Slated to be fixed in 5.0.0. See here: angular/angular@5.0.0-beta.3...5.0.0-beta.4

and

angular/angular#18641

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
2.1.0 bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Tenemo @Tynarus