Wrong image sprite paths

[andersrosten]

I'm using WebEssentials and SASS to generate image sprites, and is having problems with the resulting paths to the generated sprite .png files. WebEssentials is using node for compiling .scss files and Adeel Mujahid which wrote this comment to my WebEssentials issue:

madskristensen/WebEssentials2013#1084

WE uses following node command for compiling SCSS:

node node-sass --source-map c:/path/to/output/file.css.map --output-style=expanded c:/path/to/input/file.scss --output c:/path/to/output/file.css

The problem is; SASS compiler is not fixing the image URLs from imported document in the resultant CSS. Instead, its pasting them as is. For correct behavior, compare with LESS compiler.

Please report this bug at node-sass repository https://github.com/andrew/node-sass.

[LaurentGoderre]

This is the behavior that sass uses so perhaps it needs to be filed with the sass project.

[LaurentGoderre]

Hey, here is a related issue. sass/sass#1015

Given that it's the defined behavior of the language I don't think we can fix

[am11]

Stylus has --resolve-url switch. We can implement similar switch in node package which would auto-fix the URLs in resultant CSS file (post-processing). It would suffice both needs; sanity and language specs. :)

BTW, in lessc, they have --relative-urls switch. If you don't want it to resolve your URLs, just drop that switch from command. So I don't agree with the guy claiming he stopped using LESS because it auto resolve URLs..

[michaek]

@LaurentGoderre @am11 Do you think we should remove the wontfix label or close this issue? I don't think this is a make-or-break feature, and I'm not sure it would belong in node-sass if it was.

[am11]

Couple of changes have been made since. In WE, we are moved to code based usage (as opposed to CLI).

Secondly auto-curating url() paths w.r.t the location of generated CSS is a feature request opened in libsass' issue tracker: sass/libsass#532.