Inline Sourcemaps

[mchambaud]

It would be very nice to have more flexible source maps options available.

Something like this.

auto - relative paths where possible, file URIs elsewhere
file - always absolute file URIs
inline - include the source text in the sourcemap
none- no sourcemaps

[dbashford]

👍

[chrisspiegl]

+1

[am11]

This corresponding PR is #591.

I am testing on Windows 8.1.1 x64 with node.js x86 (you can test it with node -p "process.arch") and Windows 8.1.1 x64 with node.js x64, both with VS2013 Update 3, Python 2.7.8 and node-gyp (npm install node-gyp) installed. To test on Ubuntu, see node-sass' travis.yml file; to update GCC for c++11.

You are welcome to test on several operating systems. 😄

/cc @mgreter

[mgreter]

Basically everything has been implemented beside
always absolute file URIs

[am11]

Not sure what is the use case for abs. URIs?

[mchambaud]

@mgreter @am11 I'm not sure about use cases for absolute URIs either... but

SASS Reference

:auto uses relative URIs where possible, assuming that that the source stylesheets will be made available on whatever server you’re using, and that their relative location will be the same as it is on the local filesystem. If a relative URI is unavailable, a “file:” URI is used instead.

:file always uses “file:” URIs, which will work locally but can’t be deployed to a remote server.

:inline includes the full source text in the sourcemap, which is maximally portable but can create very large sourcemap files.

:none causes no sourcemaps to be generated at all.