Closed peterschmiz closed 10 years ago
Hi,
I need to have my gems installed locally for every project, because I have to still use SASS 3.2.19 and SASS 3.3.
On Windows I can do this only by installing gems with --path [local path]. It works well, because I use bundle exec to start these gems.
bundle exec
Unfortunately grunt-contrib-sass only checks for globally installed SASS :( So I get error, because I don't have it globally.
grunt-contrib-sass
I checked the source code ( sass.js):
sass.js
try { which.sync('sass'); } catch (err) { ... }
The bundleExec argument should be checked before that and run this check with bundleExec. Can this check be changed?
bundleExec
Cheers, Peter
It will probably please you that this is fixed in master.
Needs a new version though.
Ohh, thanks, didn't checked it! Sorry for that! Can't wait the next release :)
I'll do a new version later today.
Hi,
I need to have my gems installed locally for every project, because I have to still use SASS 3.2.19 and SASS 3.3.
On Windows I can do this only by installing gems with --path [local path]. It works well, because I use
bundle exec
to start these gems.Unfortunately
grunt-contrib-sass
only checks for globally installed SASS :( So I get error, because I don't have it globally.I checked the source code (
sass.js
):The
bundleExec
argument should be checked before that and run this check withbundleExec
. Can this check be changed?Cheers, Peter