(edited by @nex3)
I've recently wanted to start including .css files and have them parsed as Sass. The idea behind this is that a component might be added to the project as a third-party component and I'll want to import their CSS for use in Sass.
This would allow us to have project in Bower (and other package managers) for reusable CSS components that would work with or without Sass. Take the Normalize.css file for example, I would like to be able to add this to a project using Bower and import it into the project as I would an SCSS file rather than creating a vanilla CSS import.
I imagine this would mean letting this syntax:
look for normalize.sass, normalise.scss or normalize.css and pull it in. Currently it will ignore it if it only finds a css file.
Would there be any downsides to this?
/cc @chriseppstein
(edited by @nex3)
I've recently wanted to start including .css files and have them parsed as Sass. The idea behind this is that a component might be added to the project as a third-party component and I'll want to import their CSS for use in Sass.
This would allow us to have project in Bower (and other package managers) for reusable CSS components that would work with or without Sass. Take the Normalize.css file for example, I would like to be able to add this to a project using Bower and import it into the project as I would an SCSS file rather than creating a vanilla CSS import.
I imagine this would mean letting this syntax:
look for
normalize.sass,normalise.scssornormalize.cssand pull it in. Currently it will ignore it if it only finds a css file.Would there be any downsides to this?
/cc @chriseppstein