You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now the tool requires you to pass in straight css. Possibly identify and convert scss and less - as long as that won't blow up the bundle too much in size (as it's already very large -- because of d3(?)).
The text was updated successfully, but these errors were encountered:
pocketjoso
changed the title
Handle scss and less files
Handle scss and less
Nov 12, 2014
Would be cool to convert from Sass etc. and preserve the sourcemaps, because then you'd be able to point out the specificity directly in the .scss/.sass file.
I guess converting it to CSS would be the easiest for you since you can use the same parser-logic for both Sass, LESS, Stylus etc.
then you'd be able to point out the specificity directly in the .scss/.sass file.
I presume that you mean by displaying at what line in the source file the selector appeared, am I right? Wouldn't work for minified files, but that would be okay.
Right now the tool requires you to pass in straight
css
. Possibly identify and convertscss
andless
- as long as that won't blow up thebundle
too much in size (as it's already very large -- because of d3(?)).The text was updated successfully, but these errors were encountered: