-
Notifications
You must be signed in to change notification settings - Fork 6.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Theming mixins/variables massively duplicated in release output #3931
Comments
I wonder if there is a way to just import and export the themes form there, instead of using gulp to just copy the contents over. |
Looks like an issue with the scss bundling tool we're using. I filed an issue there: reactway/scss-bundle#16 |
* Updates to a more recent version of SCSS-bundle that has support for deduping. The dedupe process is very naive and only disallows importing a file multiple times. * Switches to the programmatic API of `scss-bundle` * Removes unused functions and imports / leftovers. Fixes angular#3931
* Updates to a more recent version of SCSS-bundle that has support for deduping. The dedupe process is very naive and only disallows importing a file multiple times. * Switches to the programmatic API of `scss-bundle` * Removes unused functions and imports / leftovers. Fixes angular#3931
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Bug, feature request, or proposal:
Bug? Proposal?
What is the current behavior?
In the output _theming.scss, there is massive duplication of the palettes and mixins.
The 756 KB file can be brought down to ~82 KB by removing the duplication.
What is the use-case or motivation for changing an existing behavior?
I don't really know/understand how big of deal this is. I guess it slows down npm download times and takes up 600 KB+ more disk space than required.
Related to #3776
The text was updated successfully, but these errors were encountered: