Set the sourceMap path if the sourceComment was 'map'

[sindresorhus]

See https://github.com/sindresorhus/grunt-sass/pull/61/files#diff-27568616eb678531b1ccb957e1b8aaebR17

The logic should be moved from the bin to node-sass so every consumer doesn't have to reimplement that logic.

[adamyeats-zz]

This looks to be slightly more problematic than I first thought. As sass.js does not receive an outFile path (instead we leave it up to the consumer to decide where and how to write the outFile), there is currently no way we can know where the sourcemap should be written without explicitly passing the outFile path to sass.render().

@andrew @sindresorhus If the condition options.sourceComments === 'map' && !options.sourceMap is true, I am proposing we just throw. Does anyone have any thoughts on this?

[andrew]

Yeah it doesn't look like this going to work, not really sure how to proceed tbh.

[adamyeats-zz]

@andrew In the interest of getting the issue solved, my opinion is that we should throw. I would like to hear @sindresorhus' opinion, however.

[sindresorhus]

Yup, throw with an helpful error message on how to resolve it.

[am11]

A lot has been changed since.

• OutFile is now passed to libsass (so it can calculate correct URLs in source maps).
• Libsass is using C99 bool for sourceComments (no more int).
• The semantics have been changed:
  • sourceComment: map would generate map file with sourceMapURL in CSS file.
  • sourceComment: map with omitSourceMapUrl: true will drop the sourceMapURL would generate map file with sourceMapURL in CSS file.
  • sourceComment: normal will generate inline comments in CSS,
  • souceComment: normal and sourceMap: <abs-or-rel-path-to-file> would generate both source-map file and inline comment.