CssNext Replacement

[jescalan]

Cssnext is currently severely bugged, and generally not as well maintained as we'd like, so we're replacing it with a list of individual plugins from it, which include the vast majority of its functionality.

[coveralls]

Coverage decreased (-86.8%) to 13.158% when pulling 7a04ca7 on replace-cssnext into 240464c on master.

[coveralls]

Coverage decreased (-86.8%) to 13.158% when pulling daa6be5 on replace-cssnext into 240464c on master.

[calebeby]

Yeah, I think this is a good change.

[jescalan]

You mean other than the 86% coverage decrease? 🧌

[calebeby]

Yeah...

[coveralls]

Coverage remained the same at 100.0% when pulling 1f9840b on replace-cssnext into 240464c on master.

[dbox]

👏 🙇

[01ivr3]

Do I have this correct, you guys decided to break apart cssnext and and only load a subset of it's functionality in the default spike-css-standards plugin pack? If so, should this be reflected in Spike's CSS Standards documentation to clearly indicate which features of cssnext are currently included and which are not?

Edit: or at least indicate only a subset is included and reference the plugin packs git repository to warn users they'll need to keep track of which features are missing?

[jescalan]

Yep, exactly. cssnext was having some issues, and we took a bit more of an active approach to maintenance. Good catch though, I'll update this in the documentation!