Source maps for CSS

[ai]

As I understand from docs, Parcelify doesn’t support sources map yet.

[ai]

/cc @dgbeck

[dgbeck]

Hi @ai ! It is actually browserify that works this magic. Just use the --maps option (command line) or pass { debug : true } as the browserifyBundleOptions option (api) and you should be all set. Is that what you were looking for?

[dgbeck]

Sorry, just saw the title of this issue.

We have not yet contemplated css source map support. For our own projects we use cartero which leaves each css asset separate in dev mode, so debugging is already easy and we have not had any need for source maps.

This feature would be a challenge to implement in parcelify. You would have to generate the source map yourself, maybe using the ones generated by sass as building blocks, since parcelify is concatenating all the css files. Also in order to make this modular it would need to be implemented mostly as a transform. I think it would be possible, for example by using sass-to-css-stream as a starting point, but I sense devils in the details. We would also need to add a hook to parcelify so that we could dump a .map file once everything has been concatenated.

I'm not opposed to adding this functionality and would gladly review a PR, but right now it is not on our priority list. cartero already fills this need for us quite adequately.