Update WP4 Version with Legacy Features/Tooling

[bignamehere]

If you do not have Webpack 4 installed, follow these instructions.

Below is a list of features to verify and/or include in the WP4 version of the FSA Style codebase.

• clean

• copy (primarily to bring in USWDS assets).

• watch

• browsersync

• prettify (html)

• style-loader / css-loader

• SCSS source map

• stylelint

• min (i.e. fsa-style.css and fsa-style.min.css)

• postcss (and associated plugins)

  • autoprefixer
  • pixrem
  • postcss-quantity-queries

• usebanner (currently used for version comment line of fsa-style.[min].css)

• Compress to published ZIP

• What else excites us?

  • prettier, possibly in place of prettify
  • CSS Next (unlikely, but worth exploring)
  • hot-module-replacement. Not exactly a "live-reload" (or browsersync) analog, but still interesting
  • Basic "includes" to piece together Kitchen Sink (index.html) listing (future: templating etc)

[bignamehere]

Updated and verified if Autoprefixer was working correctly. (see b511588)

[bignamehere]

Need to implement BrowserSync... here is the link to the repo

https://github.com/Va1/browser-sync-webpack-plugin

[bignamehere]

Legacy Issue located here

[bignamehere]

FSA Prototype Kit implements a feature to enable pixrem for legacy browsers.

[bignamehere]

In theory, you could use the Webpack configuration that ProtoKit uses to recreate.

[whatnextjamie]

@bignamehere close this one too?

[bignamehere]

@whatnextjamie actually keep this one open, as it has the list of “requirements” that we should try to adhere to for a build system.