Codecov Report

Attention: Patch coverage is 66.43836% with 49 lines in your changes are missing coverage. Please review.

❗ No coverage uploaded for pull request base (main@2745167). Click here to learn what that means.

@@           Coverage Diff           @@
##             main     #133   +/-   ##
=======================================
  Coverage        ?   63.55%           
=======================================
  Files           ?       43           
  Lines           ?     2854           
  Branches        ?      404           
=======================================
  Hits            ?     1814           
  Misses          ?     1013           
  Partials        ?       27           

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

@qwerzl That was quick! Would it be possible to also specificy custom values for the font variations. Currently it's set to opsz,wght,FILL,[email protected],100..700,0..1,-50..200 but with the possibility to add our own values here we can substantially reduce the size of the file that is being requested. As an example this is our current font variations allowing for the smallest file size possible: :opsz,FILL@20,0..1

@AndersCV Would there be a way to detect what you need without configuration, do you think? What does your usage look like?

@danielroe

Currently we're using the "@nuxtjs/google-fonts": "3.0.2", module to request our font files with this config in our nuxt.config.ts

googleFonts: {
    display: 'swap',
    families: {
      'Material Symbols Rounded:opsz,FILL@20,0..1': true,
    },
  },

In our case we have a simple <Icon> component that accepts only one prop which is "fill: 0 | 1" because our design makes use of icons with both fill: 0 and fill: 1.

This is purposely done so we can request a font file that is as small in file size as possible, otherwise the whole material symbols font file can be several MBs which is not great. Ideally we would like to reduce the file size further by somehow only including the nessecary icons, but I think thats beyond my expertise. I think our current file size comes down to 440~kb.

Detecting this without some form of configuration I don't think is possible as the font-family is applied inside our custom component.

I guess the first thing we should do is to support setting variable weight ranges. Currently every variable font is defaulted to maximum weight ranges for every provider.