cedaro / grunt-wp-css Goto Github PK

Currently, the process is:

1. copy test/fixtures/* to tmp/* (requiring grunt-contrib-copy).
2. Run wpcss over tmp/* src and save to tmp/* dest.

Since wpcss can save to a new destination already, why not:

1. Run wpcss over test/fixtures/* src and save to tmp/* dest.

and avoid grunt-contrib-copy dependency altogether?

Basically, the same issue as cedaro/grunt-wp-i18n#40 .

According to the CSSBeautify website, all that CSSBeauty can do is:

Only one blank line between two rulesets
Closed curly brace is at its own line
There is no empty line between declarations inside a ruleset
No space between the property name and colon
One space between colon and the property value
Comments are preserved

CSSComb can cover pretty much all of that already, and where it can't, we could enhance the contents.replace() calls that already exist. That way, we're only passing the source through two process (csscomb and custom replacements) instead of three, which would make debugging considerably easier.

Disabling the call to cssbeautify() does currently make the comments_spacing test fail, hence the need for tweaking the custom replacements slightly.

I've been working on getting source maps working for our theme and plugin configs and i think I've manged to trace the issue back to this module.

Has anyone else run into issues with source maps being inaccurate/broken after the file is run through grunt-wp-css?