Skip to content

Conversation

@slifty
Copy link
Contributor

@slifty slifty commented Jan 16, 2026

This PR changes the way we use ionicons to use their web component library. This allows us to remove packaged vendor scss and also means that our application will benefit from tree-shaking / won't include icons that aren't being used in the code base.

This PR does update to the most recent ionicons (we were using v4, and it is now v8). For the most part the icons are very visually similar, but there are some cases (e.g. folder) where you will notice a difference if you look side-by-side.

Resolves #893

@codecov
Copy link

codecov bot commented Jan 16, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 47.79%. Comparing base (ce15770) to head (e30817f).

Additional details and impacted files
@@                 Coverage Diff                  @@
##           noissue-fix-info     #894      +/-   ##
====================================================
+ Coverage             47.76%   47.79%   +0.02%     
====================================================
  Files                   351      351              
  Lines                 11292    11292              
  Branches               1889     1889              
====================================================
+ Hits                   5394     5397       +3     
+ Misses                 5709     5702       -7     
- Partials                189      193       +4     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@@ -1,24 +1 @@
.ion-custom-folder-move {
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It looks like these styles weren't actually being used anywhere.

@slifty slifty force-pushed the 893-ionicons-web-components branch from ebdb2fe to 8c541e3 Compare January 16, 2026 15:13
@slifty slifty force-pushed the 893-ionicons-web-components branch from 8c541e3 to f28de58 Compare January 16, 2026 15:16
This was referenced Jan 16, 2026
@slifty slifty force-pushed the 893-ionicons-web-components branch from f28de58 to be10eb6 Compare January 16, 2026 17:29
We were using embedded SCSS from ionicons instead of their recommended
approach which is to use web components + their npm package (though we
WERE using their npm package).

Issue #893 Move to ionicons web components
@slifty slifty force-pushed the 893-ionicons-web-components branch from be10eb6 to e30817f Compare January 16, 2026 21:11
@slifty slifty changed the base branch from main to noissue-fix-info January 16, 2026 21:11
Base automatically changed from noissue-fix-info to main January 17, 2026 02:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Move to ionicons web components

2 participants