Ayu

Closed in #824 and #826.

Closed in #590 as we no longer use Got and use native fetch. Check out the new [CLI](https://github.com/fontsource/fontsource/tree/main/packages/cli) or [font-files](https://github.com/fontsource/font-files) repo for your usecase.

You can now use [CSS variables](https://fontsource.org/docs/getting-started/display) to change `font-display` in v5! 🎉

I don't think this is necessary anymore with the new CLI from #590. If we are missing features, we can plan to extend that.

We've rewritten the Sass integration entirely for [v5](https://fontsource.org/docs/getting-started/migrate-v5) 🎉 Please let us know if you run into any issues!

Changed in [v5](https://fontsource.org/docs/getting-started/migrate-v5) 🎉 We no longer export the material icons class and leave that to the user's responsibility.

Closed in fontsource/font-files#1.

Yup, I can confirm it is definitely a Windows only bug. This is a current [workaround](https://github.com/fontsource/fontsource/blob/main/packages/publish/scripts/add-hashbang.ts) I have for all my packages in the meantime which runs after every build.

This would _significantly_ reduce the size of my [generated source files](https://github.com/medama-io/medama/blob/main/core/api/oas_parameters_gen.go) and improve debuggability since I [reuse a lot of my parameters](https://github.com/medama-io/medama/blob/main/core/openapi.yaml#L487) over many endpoints. Although I'm not 100% sure...

I think this idea may unintentionally affect many builds with older bundlers and potentially be breaking for some of them. I'm a little uncomfortable making such a change without knowing...