-
Notifications
You must be signed in to change notification settings - Fork 2.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
Update icons to v3.70 #12088
Update icons to v3.70 #12088
Conversation
Asset size changes
Baseline commit: c7c4b6098eea407a37897279d953a42a11ccea86 (build) |
Perf AnalysisNo significant results to display. All results
Perf Analysis (Fluent)Perf comparison
All perf tests
|
Size auditor is failing -- @KevinTCoughlin do the icon additions actually have any impact on bundle size for you, or do you use custom subsets? |
Apologies for the delay @ecraig12345. First-party SharePoint code utilizes https://www.npmjs.com/package/@microsoft/office-ui-fabric-react-bundle which does the following: export * from 'office-ui-fabric-react/lib/Icon'; The majority of third-party developers currently bundle I anticipate the Regarding run-time cost, at least it is a "simple" structure to parse. Linear increase in memory is a greater concern. See the below memory dump from SPO containing all Fabric Icon strings. To address, SharePoint would have to export and utilize an icon sub-set as you mention. @Jahnp perhaps you can consider this improvement if you anticipate additional revisions to this package. |
@Jahnp Is this still needed? It seems there are conflicts, looks like the url may have changed? |
Sorry for letting this linger. This PR is very stale at this point and many new icons have been made available since this was opened. I'm going to go ahead and abandon this for now. Additionally, @KevinTCoughlin brings up some excellent points about the downstream impact of the constantly-growing icons package's bundle size on users of SPFx and similar solutions. I agree with the concerns and think it's probably best to avoid continued revisions like this that simply add new icons. Within SPFx, it would likely be best to investigate a custom icon subset. Further, I'm inclined to stop updating the default icon set in this manner and instead recommend that users looking for new icons should consider custom icon subsets with the Fabric icons tool instead. |
Pull request checklist
$ yarn change
Description of changes
Updating @uifabric/icon's icon set to the latest version from the Fabric icons tool, v3.70. This PR adds new icons from that version to the "chunked" subsets that get automatically loaded on usage. There may also be visual updates to some icons.
Apologies - I know this has a lot of changed files, but it can't really be batched. The core code/asset changes are under
packages/icons
.Microsoft Reviewers: Open in CodeFlow