Mario Ranftl

Sorry can't help here. All font files are gathered directly from google's CDN (`fonts.googleapis.com/css?`) with our pinned [USER_AGENTS](https://github.com/majodev/google-webfonts-helper/blob/master/server/logic/conf.js). No post-processing is happening here.

We currently only link to the [Google Fonts attibution page](https://fonts.google.com/attribution) in the instructions (right beneath the download button), but you are absolutely right. Need to take a look if their...

Yep that's intentional, `unicode-range` was a thing of the future when this project was initially released (the user-agent to grab the `woff2` files is quite old). Will mark this as...

see `.nvmrc` --> `0.10.44`, I know this is quite an old project now. Supporting [Node.js LTS](https://github.com/nodejs/Release) is not planned currently, maybe with the next full refactor.

Not sure if this is required as we don't convert / repack them in any way actually, these are the exact same files you would be requesting if you are...

This would definitely be awesome and will be part of the incoming next major rewrite. I want the server+client to share the same implementation of the generation logic (and also...

Hi, looks like it stabilized again. Typically I see these problems if the upstream google fonts API has issues. Also see https://github.com/majodev/google-webfonts-helper/issues/151.

Better late than never, I will have look at it in the incoming days. I must make sure first that Google's API delivers them...

Hi, I also think automatically tagging with `latest` or another label (e.g. the name of the branch that was pushed) would be the most convenient workaround for these cases.

Note that this feature would be especially important for editor integrations like VSCode's [vscode-go](https://github.com/golang/vscode-go/blob/master/docs/settings.md#golintflags). Users have no option to control the cwd from which `golangci-lint` will be executed there (lint...