Ayu
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!
Released in [v5](https://fontsource.org/docs/getting-started/migrate-v5) 🎉
This was closed way back in #590.
> You shoud first document what this Our entire versioning strategy is. It is documented at the top of [`CHANGELOG.md`](https://github.com/fontsource/fontsource/blob/main/CHANGELOG.md). As mentioned in this issue, it's close to Semver, but...
Here's my main concern and why I wrote a custom publisher. Does it scale well? If Fontsource pushes a minor release, we end up publishing over 1500+ NPM packages in...
> because if it's a. Then it doesn't matter. Now that I've reviewed it again, yeah the versioning strategy doesn't matter. It would work fine in that regard. Awesome project,...
> But i suppose you knew that, which means you want everything deployed again when one package changes? Patch releases will affect individual packages - that's not an issue. Minor...
Now that we switched over to a completely different monorepo setup for V5, Changesets became feasible to run over the small number of utility packages we have here and I...
Released in [v5](https://fontsource.org/docs/getting-started/migrate-v5) 🎉
Appreciate the original issue, but I think I'll close this issue to clean up some of the stale issues in this repository. If this ever comes to fruition, feel free...