Path issue in Windows

[tijtij]

Don't know if this is an issue with the Bourbon example, brackets-sass, or libsass but compiling is broken when the project files are located on my D drive.

This is what app.css.map looks like:

{
  "version": 3,
  "file": "app.css",
  "sources": [
    "C:/D:/bourbon-example-master/scss/app.scss",
    "C:/D:/bourbon-example-master/bower_components/bourbon/dist/_bourbon.scss",
    "C:/D:/bourbon-example-master/scss/partial.scss",
...

Previously reported in issue #21 (comment)

[ofhouse]

Same here.
Found out that the issue was caused by this code.
Unfortunately I'm not really experienced with Node.js so I don't know how to debug Node.js code to fix that :
console.log() / Webkit Dev-Tools doesn't work here.

Edit: It's a bug related to path.resolve(), more details here.
Think it needs a workaround for this behavior.

[nicolo-ribaudo]

Fixed: #99

[jasonsanjose]

FWIW the path that we get from the source map returned from node-sass will typically look like this:

../../../../../../../../../../D:/bourbon-example/scss/partial.scss

The bug happens when the input file and some included path are on different drives.

[jasonsanjose]

Closing. Targeting v2.

[jasonsanjose]

See test build here #100 (comment) with path fixes for both libsass and ruby. Targeting for v2 release.

[jasonsanjose]

Re-opening since PR #100 hasn't been merged yet.

[jasonsanjose]

@tijtij there's a test build you can try here https://github.com/jasonsanjose/brackets-sass/releases/tag/2.0.1-105. If you have some time, please let me know if that fixes your problem.

[tijtij]

@jasonsanjose Works for me on Brackets 1.20-15697.

None of sources paths in *.css.map are using drive letters.

Thanks for the fix.