A sass' file structure generator
A pure JavaScript implementation of Sass.
Sass loader for webpack
A language engineering tool for the Language Server Protocol
Node.js library that communicates with Embedded Dart Sass using the Embedded Sass protocol
The linux-x64 binary for sass-embedded
The linux-musl-x64 binary for sass-embedded
Find the dependencies of a sass file
Determine if a function is a native generator function.
Get the file associated with a Sass import
Turns an AST into code.
A small tool to find unused Sass variables
Turn async generator functions into ES2015 generators
A function that returns the normally hidden `GeneratorFunction` constructor
Sass/SCSS language support for the CodeMirror code editor
Turn async functions into ES2015 generators
Helper function to remap async functions to generators
A Sass parser for PostCSS, using gonzales-pe.
Lezer-based Sass/SCSS grammar
Parse sass files and extract a graph of imports
TypeScript Sass formatter
The linux-arm64 binary for sass-embedded
The pure js optional dependency for sass-embedded
The pure js optional dependency for sass-embedded
<p>Sass or the much better approach of scss is really helpful and a big silver bullet for my css structuring in ruby projects.</p> \ <p>Standard sass command works for whole directories or single files only. In general it gets the jobs we want done, but in practical usage i think the sass command tool is a little bit unconvinient. A common scenario for me is, \ that you have whole bunch of sass files, which you want to compile to a single compressed output file. But if you have splitted your sass files in component based modules and you want to watch the complete folder you have to care for dependency handling in each file, because each file will be compiled for its own.</p> \ <pre># compiling a complete folder with scss ~ $ sass css/scss:css/compiled</pre> \ <p>So converting the whole folder is not what i want, because i don\'t want to import for example my color.sass config file in each module again. Compiling a single file seems to be the better solution, and it works in general, as expected, but the devil is in the detail. </p> <pre># compiling a single file where the other files are imported. ~ $ sass css/scss/main.scss:css/compiled/main.css</pre> \ <p>If we change a file with impact to our main.sass file, the --watch handle will not get it, because it observes only the timestamp of the given main.sass.</p> <p>Here is it, where mindful_sass tries to help out. You use it according to the single file variant of sass, but it tries to observe the whole folder the given sass file is placed. If a timestamp of file in the sass folder or its children changes it will compile the specified main.sass again.</p> \ <p>This gem is not aimed to replace anything in the sass universe. It is only a wrapper to avoid the described unconvinience, and i hope that it gets useless as fast as possible, because the sass development gets this feature done for themselves.</p> \ <p>Thanks anyway to the sass developer team.</p>
This is a hacked-together version of the gem 'bootstrap-sass', with the generators from 'twitter-bootstrap-rails', has also replaced the Glyphicons icons with [Font Awesome](http://fortawesome.github.com/Font-Awesome/), since svg icons are resizable and colorable and such. There are also some custom scss helpers in a folder called 'custom_partials', which are just a byproduct of trying not to hate css. The nature of those scss helpers are very similar in look and feel to the bourbon gem by thoughtbot, which seems more complete than my own (to be honest) but when I had started accumulating helpers, I was not aware of the gem. Feel free to muck around with this as you please.