Mike Crantea

@miina I've handled the 8 conflicts and issued a PR against this branch here which handles them: https://github.com/ampproject/amp-wp/pull/3931 This is an effort towards getting it closer to being merged.

@loganwisniewski please contribute a PR which updates all of the dependencies to the latest versions. If there are libraries still relying on a vulnerable version we can create a ticket...

The bug in core is still existing - https://core.trac.wordpress.org/ticket/51136 Can this get merged any time soon?

@westonruter I did not use a SCSS validation tool as the compiler is the first line of defence in catching errors. The compilers never generates invalid code. At the slightest...

I gave http://csslint.net/ a try. And through 270 warnings I got from the stylesheet generated, I noticed 12 valid items which I had included in improving the code base. But...

An SCSS validator would only make sense if we're compiling the SCSS files on the server, as long as this thing is happening locally, it's not a requirement to be...

Stylelint seems to be a wee bit more modern than the CSSLint I just tried earlier. http://benfrain.com/floss-your-style-sheets-with-stylelint/ Funny how the author went _"I go friggin’ ape if someone doesn’t put...

@kopepasah I would expect the configuration file to be filled in on a per-project basis, as the paths are always unique. And one can eventually turn on/off features using flags...

This is being worked on in https://github.com/xwp/wp-dev-lib/pull/245 We've done good progress on a general FE workflow, but the scripts can be further improved upon once we start using this in...

Yepp, I can and I will.