Incorrect mapping of sourcemaps using node-sass@1.1.4

[dwayne-roberts]

@dlmanning I decided to update gulp-sass to 1.2.2. today and noticed that all my css classes mapped to incorrect scss sourcefiles and/or line numbers. Figured it had to be something that changed. I'm no JS wizzkid but I checked your dependencies and noticed you're using the relaxt ^ instead of ~ for node-sass. dependency.They recently bumped from 1.0.3 to 1.1.4 and with ^1.0 it would require the new 1.1.4 version. If I use the 1.0.3 version the problem is resolved.

[booleanbetrayal]

+1 ... FWIW, here's a discrepancy I'm seeing between gulp-sass 1.1.0 and 1.2.2 map output:

1.1.0

"mappings": "4DAEA,KAOE,YAAa,WACb,qBAAsB,KACtB,yBAA0B,MAG5B, ... ... ...

1.2.2

"mappings": ";;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;4kHAEA,KAOE,YAAa,WACb, ... ... ...

haven't been able to dive into any deeper, but something tells me that the string of semi-colons is not intended. =]

[ByScripts]

I confirm. There is a lot of ;;;;;;;;;;;;;;;;;;; generated, and the mapping is completly wrong (Chrome console shows and brings me to a totally wrong place for example)

[adam-beck]

+1

I'm having the same issues and noticed the semicolons.

[adam-beck]

This is probably an issue all the way upstream in libsass. Here are related issues:

node-sass issue #565
libsass issue #324

[Snugug]

As this is an upstream bug, I'm going to close this issue.