Open jcandan opened 1 year ago
Facing the same issue - buildSass()
has some hard-coded configs that we wish were available to override.
I am going to look into a way to patch the original file to make that possible.
CC @mejiaj @mahoneycm
@jcandan thanks for submitting this issue!
A few questions to clarify the request…
Can't you set this currently via uswds.paths.dist.theme
or paths.src.projectSass
?
// your-gulpfile.js
uswds.paths.dist.theme = "src/stylesheets/mywds.scss"
// Alternatively, other project SASS files.
uswds.paths.src.projectSass = "src/stylesheets/mywds.scss"
includePaths
and outputStyle
This is a good idea and we should include. Captured in #80 and #113.
uswds.paths.dist.css
You should be able to do this via the setting.
// your-gulpfile.js
uswds.paths.dist.css = "./another/folder/to/save/"
Captured in #80.
Is your feature request related to a problem? Please describe.
I have built the beginnings of a USWDS 3 custom design system package. Instead of using USWDS on a single project, and customizing it each time we use it in a new project, this will lay the foundation for us to have consistency across organization projects.
Describe the solution you'd like
To accomplish this, it was necessary to override the
buildSass
function.So, it seems then that we need:
includePaths
key of thebuildSettings
object, and setoutputStyle: "expanded"
.uswds.paths.dist.css
.Describe alternatives you've considered
No response
Additional context
With this change, we could document how an organization can build their own USWDS packages to support their entire organization. This also opens up the possibility for community driven packages.
Code of Conduct