Ayu
Although I'm a bit late to this conversation, I'd love to hear in what ways I can add to or change the Fontsource API to better support your usecases if...
> instead of passing Reuse plus the container name, we don't need to pass a container name anymore, only the Reuse field. This is a breaking change in terms of...
I think it’s worth tracking this as it is an actual bug, so let’s keep this open. I’m following the main TS thread first before making any decisions.
Note I think there is a valid workaround such as importing `@fontsource/roboto/index.css` or alternative CSS files (e.g. `@fontsource/roboto/400.css`) directly with their extension instead of pivoting to Sass.
I think it makes sense when importing via the CDN, but usually its normal for bundlers to minify everything for us. I'm not against the idea though. > having these...
Comparing the Fontsource and Google Fonts previews, it seems correct? Do you experience this when using the variable version of these fonts?
Can you reproduce this with `@fontsource-variable/noto-sans-kr`? I have a feeling it’s related with aliasing issues that probably wouldn’t be present in the variable variant.