Ayu
Isn't it just changing [this line here](https://github.com/privatenumber/pkgroll/blob/572c417039566f79f87ab62b42ecbd9d3f7d73bb/src/cli.ts#L39) from `node${process.versions.node}` to `node14`. Or am I missing something here? I'll be happy to PR it just to start getting my hands involved...
I was working on this but privatenumber/eslint-config#33 is a blocker. Will wait till that's resolved!
Food for thought, but I think one really interesting metric would be measuring individual exports so you can get it's tree-shakened size. I don't think that's an easy thing to...
Just for future reference, but I think this project does implement all the treeshaking logic discussed before using esbuild and could be a useful baseline: https://github.com/okikio/bundle
Out of curiosity, what's the roadmap/when do you expect to be feature-complete? Or that's still TBD?
That looks great! I can't wait!
> Based on how huge the browser support for variable fonts is, I would like it even more if the variable fonts just use the same name as the non...
In the end, I went back to using different names as we needed a reliable way to write [fallbacks](https://fontsource.org/docs/getting-started/variable#4-fallbacks). Released in [v5](https://fontsource.org/docs/getting-started/migrate-v5) 🎉
> Could there be an alternative css file that doesn't have the "Variable" suffix? We can't generate more CSS files and pack it into the package. That would end up...
Fixed in [v5](https://fontsource.org/docs/getting-started/migrate-v5) 🎉