Testing css

[djmtype]

During development, npm run watch, how is one suppose to test css if the code has been minified? There are no line references because everything is on line 1.

[cramforce]

The CSS should be unminified. There really is no good reason for the current state since it gets re-minified during build.

[djmtype]

@cramforce True, the css isn't minified in the css file, but it does get transformed/minified (probably due to csso) during development – npm run watch. Therefore, there is no real frame of reference when troubleshooting.

[cramforce]

Should be totally possible to generate a sourcemap!

[djmtype]

@cramforce CSSO provides an option, but then the css gets parsed through PurgeCSS anyway, I think.

Please don't keep me in suspense. How can we add a css sourcemap for npm run watch only?

[cramforce]

I filed FullHuman/purgecss#526

There is, indeed, little that can be done for now short of turning off CSS purging during development.

[theor]

I've disabled css inlining in dev mode, as it allows browsersync to inject css and bypass 11ty, which is way faster. is it something worth a PR ?

[cramforce]

I don't think I want to make that a default, but otherwise it is worth a PR for sure!

[theor]

#108 let me know what you think !