What's new in USWDS 2.2.1
Sass compiles properly: Now importing
@import uswds will compile properly. The
packages/uswds-components package newly referenced by
uswds.scss was using incorrect paths and now they point to the proper locations.
Why did this happen? A quirk of how Sass evaluates paths prevented us from seeing this error before we published the release. Sass will, apparently, accept paths relative both to the the file containing the
importand also to the entry point (ie, the primary file the compiler points to). The incorrect
/basepaths evaluated properly for us internally since
uswds.scssis the entry point from which we compile our Sass (that is, we do not
@import uswdsfrom a separate file). By chance,
/baseis valid relative to this internal entry point.
How are we preventing this in the future? We've made the build process more strict in
uswds-site(uswds/uswds-site@103dd3f#diff-d0940386a71c685fc307161a767958b4R54) so it'll be far less likely that such a bug will make it through our testing. We may also change our internal build process to surface errors such as this one.