-
Notifications
You must be signed in to change notification settings - Fork 135
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is there any plan to create grunt plugin for sass.js? #61
Comments
Nope. Maybe simple-sass (CLI for sass.js) helps? |
I created an initial grunt plugin https://github.com/amiramw/grunt-contrib-sassjs. Hope it's ok. Not yet released to npm. |
|
Thanks for the feedback. |
Thanks for your efforts!
I don't think that's the most important thing for now…
Parsing and mutating pathsThe importer callback looks like it's trying to mimic a subset of _libsassPathVariations(). Maybe we should talk about how we can expose this function so you can use it like _resolvePath()? You want to use the Path module instead of playing the string manipulation game:
Error Handling:
SourceMaps
|
Fixed most of the comments. For now I copied _libsassPathVariations(). Let me know if you export it. |
which ones didn't you fix and why?
As of 0.9.12 you no longer need your copy of I would rewrite your source map handling to var rootDirectory = "sass/" + PATH.dirname(src);
result.map.file = cssFile;
result.map.sources == result.map.sources.map(function (source) {
return PATH.relative(rootDirectory, source).replace("\\", "/");
}),
grunt.file.write(cssFullPath + ".map", JSON.stringify(result.map)); Since you're using |
At first I didn't populate the However I adopt your suggestion for Thanks a lot for the help. |
thanks for your efforts! |
No description provided.
The text was updated successfully, but these errors were encountered: