FP-1648: Build Individual Stylesheets — ⚠️ API Change

[wesleyboar]

Overview

Allow consuming and/or building* individual stylesheets.

• (for clients that only consume)
  Build all stylesheets and commit dist/ directory (for Portal).
• (for clients building from source)
  Let clients (and this repo itself now) build individual files (theirs, ours, both).*

_{* CMS is the only client app that does, and is expected to, build its styles via the Core-Styles build command.}

Related

• FP-1648
• required by FP-1647: Use Core-Styles Core-Portal#639

Changes

Top of diff and bottom of diff have the most relevant changes. In between is all dist/.

• e00d6b8 let user match pattern, drop --file-ext
• ef2db2b build all stylesheets and commit dist/
• 12f1484 use --input/--ouput not --input-dir/--output-dir
• c543a07 allow build with custom glob input
• update .gitignore

Testing

1. Build all styles internally via npm run build.
   • Verify all are added in the same sub-dirs as source/_imports/.
   • Verify dist/tools/ stylesheets have either class selectors (.bob) or functional selectors (%bob), not both.
2. Test all styles internally via npm run test (builds output of plugin tests).
   • Verify build output in dist/_tests/.
3. Test https://github.com/TACC/Core-CMS/pull/489/files.

Screenshots

N/A

[wesleyboar]

Merging based on approval of TACC/Core-CMS#489 which is on the only repo using the Core-Styles CLI.