Evaluate continued use of USWDS (including v2)

[francisrupert]

Summary

• fsa-style currently uses uswds@1.2.1
• Most current 1.x version is at 1.6.9.
• How should we move forward?

Task

• Evaluate node/npm implications of any USWDS 1.x update. How far up the 1.x version can we even update to?
• Evaluate and form opinion on any 1.x features worth integrating. Can be specific UI Components, or other core bits (e.g. SCSS, Bourbon, etc).
• Confirm a 2.x (beta) version of USWDS would break fsa-style.
• Should we consider the removal of USWDS as a dependency? Bake it in effectively? Understand pros/cons.

Background

USWDS has been a fairly core dependency of our CSS Framework since the beginning. Once 1.4 or so was released, FSA systems' version of node/npm kept us from updating. Since we strip it out a bit, and selectively use specific USWDS dependencies and UI Components fsa-style does not suffer for it.

Meanwhile, USWDS has a major 2.0 version in the works (currently in Beta). It is effectively a rewrite and likely completely breaking to fsa-style.

[francisrupert]

FYI, initial finding

Huh, updating to 1.6.12 seemed to not be an issue (the actual npm i part). It sure broke when I tried several times between 1.2 and 1.5 or something

Initial outcome:

Carefully investigate and consider:

• Straight update to uswds dependency, or
• Update and integrate to latest 1.x release and remove as dep? (Particularly because 2.0 is clearly significantly breaking).

[francisrupert]

Finding

• Retain uswds as dependency, restricted to 1.x.x, which may continue to receive updates, even parallel to 2.x.x versions.
• Version 2.x.x is incompatible and eliminated as a possible update for fsa-style as it is effectively a new codebase and wholly breaking.

Action

• [x] Create new issue to update to 1.6.12 (or latest).
• [x] Log issues of resulting new features, updates, or bugs.
• [x] Marked this issue as resolved.