jwr1

I'd go with `--fontsource-display` because it's shorter and you set it once for all fonts, if other people need to set it per-font/per-variation, they could write their own CSS and...

That does seem like a better option, as it more closely follows Rollup's API.

@antfu, I have created a new proposal that includes your suggestions and follows closer to Rollup's API. I also included a method to create new plugin instances (if they do...

@DecliningLotus, if you're still considering this issue, one option we could use to create the bundler plugin is [unplugin](https://github.com/unjs/unplugin). It's a unified plugin system supporting Vite, Rollup, Webpack 4 &...

I still feel even with this option that a bundler plugin would be useful. You mentioned this would have to be run whenever it's reinstalled, that could be done automatically...

> Would that mean developing for both cases? No, I think we could just use the original idea you mentioned and just reference the node API from within a bundler...

Also, under the Font Preview, a Flutter tab for an install guide and available parameters.

Hello @DecliningLotus, I am interested in joining the Fontsource organization. I am already familiar with some of the code contained in this repository. As you know I have contributed several...

Anyone interested in the new Sass integration can see the `mixins.scss` file [here](https://github.com/fontsource/font-files/blob/main/fonts/google/open-sans/scss/mixins.scss). I have also written documentation for the two new mixins, [faces](https://beta.fontsource.org/docs/getting-started/faces-mixin) and [generator](https://beta.fontsource.org/docs/getting-started/generator-mixin). Nothing is set in...

We can still change the mixin and parameter names too, in case someone has a better name for `faces`, `generator`, or any of the parameters.