Closed marksmccann closed 5 years ago
Apparently in the CLI, when sourceMap
is provided (either as a boolean or string), it writes it to disk. We could probably replicate the behavior on the node side? However, that would mean that it would write the sourcemaps to disk, even if the user may not want that.
I have been thinking about this for the past couple days. I like the idea of keeping parity between the CLI and the Node API. I am going to play with that option, to see how it feels – if both output
and sourceMap
are provided, both the compiled css and the source maps will be written to disk. If output
is not provided, source maps will not every be written to disk. It will not be possible to write the source maps without also writing the compiled css OR vice versa. But, that might be okay. We'll see.
We need to consider how to handle sourcemaps –
outFile
and/orsourceMap
be defaulted to the value ofoutput
when provided?outFile
and/orsourceMap
also support a function for a dynamic output whenoutput
is not desired?outFile
and/orsourceMap
also support a directory string similar tooutput
?Here are some thoughts –
In the case of ...
Would ...