Project configuration for Sass

I’d like to make a simple configuration system for running sass with the same options for a given project.

My proposal is to simply allow command line options to be specified in a hidden file called .sass in the current working directory.

GLOBAL: [options for all core commands]
--update,--watch: [options for update or watch] 
--update: [options for update] 
--watch: [options for watch]

So for example:

GLOBAL: --compass -I ../my_library_of_sass -r ./some_custom_stuff
--update,--watch: from_dir:to_dir
--update: -t compressed
--watch: -t expanded  --sourcemap

Then simple user commands can result in more complex, repeatable commands:

Typed	Command ran
sass --watch	sass --compass -I ../my_library_of_sass -r ./some_custom_stuff --watch from_dir:to_dir -t expanded --sourcemap
sass --update	sass --compass -I ../my_library_of_sass -r ./some_custom_stuff --update from_dir:to_dir -t compressed
sass -i	sass -i --compass -I ../my_library_of_sass -r ./some_custom_stuff

Any additional options typed by the user when issuing the command would simply go at the end. We could also create an option to ignore the .sass file.

Anyways, this is a strawman. I’d like to see a way to establish reproducible sass compiles to enable team collaboration even if they don’t use compass. If there are other ideas for how to do this, let’s discuss them. However, I’d like to avoid making this a ruby file.

[markusweb]

any news to this? is it possible to use a config file with sass (no COMPASS or RAILS, so config.rb or environment.rb seems not to work). there is an Option Section in the docs (http://www.sass-lang.com/documentation/file.SASS_REFERENCE.html#options) but it seems that Sass::Plugin.options only work with RAILS/RACK. so when i use stand-alone sass can i use some config files to set Sass::Plugin.options or use environment variables?

thanxs

markus #

[nex3]

Closing this in favor of https://github.com/sass/sass/issues/2669, since the details are very different in a JS-centric world.