This repository was archived by the owner on Jul 24, 2024. It is now read-only.
Repository navigation
This repository was archived by the owner on Jul 24, 2024. It is now read-only.
sourceMap option documentation is inaccurate #2394
Description
The documentation for the sourceMap option claims that
Setting the
sourceMapoption requires also setting theoutFileoption
However, in practice, if you set sourceMap to a string and don't set outFile, you still get a map buffer in the result. For example:
var sass = require('node-sass');
var result = sass.renderSync({
data: 'a {b: c}',
sourceMap: 'out.css.map'
});
console.log(result.map.toString());prints
{
"version": 3,
"file": "stdin.css",
"sources": [
"stdin"
],
"names": [],
"mappings": "AAAA,AAAA,CAAC,CAAC;EAAC,CAAC,EAAE,CAAC,GAAE"
}
Activity
ericmorand commentedon Apr 15, 2019
The Result object description is also inaccurate:
As seen on @nex3 example, when the source was not a file, the parh to the SCSS file is not data but stdin.
EDIT: Actually, I'm wrong, stats Result object is correctly returning "data" as entry path. Still it is inconsistent with the value returned in the source map "sources" which is "stdin".
Fix sass#2394: sourceMap option should have consistent behaviour
saper commentedon Oct 17, 2019
Thanks for this - there was even a small bug.
render()has always provided amapwith theundefinedvalue if the map was not requested, unlikerenderSync().Fixed via #2754
Fix sass#2394: sourceMap option should have consistent behaviour
Merge pull request #2754 from saper/no-map-if-not-requested