Evan Willhite

https://github.com/fourkitchens/emulsify/tree/develop/components/_meta

Move to Webpack

2

We've discussed this in other stories offline, but we don't have an official issue to track it to. I'm interested to explore this and see how it impacts build performance.

h/t to @jegarts. We should offer a command to kill running instances of Emulsify - something that taps into https://www.browsersync.io/docs/api#api-exit perhaps?

It appears [gulp theme](https://github.com/fourkitchens/emulsify-gulp/blob/develop/index.js#L133) just runs `gulp serve` so I'm guessing we could clean up and simplify that.

- Performance testing (WPT and PSI) - Github pages deployment - [Visual Regression Testing](https://github.com/fourkitchens/emulsify/pull/59) - Accessibility testing - Aerate as Emulsify plugin? We should make Emulsify Gulp as bare-bones as...

Sass to postcss

5

Move from Sass to postcss and provide documentation on how to add new postcss plugins as needed.

We have added automated accessibility testing in a separate PR, but this is handled per component while editing twig or scss files. We should add a way to test all...

moved lint devdeps to deps

1

Moving eslint devdependences to regular dependencies to help with adding eslint to emulsify core https://github.com/fourkitchens/emulsify/issues/115