fontsource
Font Request: Hack
Font Name
Hack is a monospaced font designed for source code that has been quite popular a few years back... It's also available on GitHub.
For some strange reason the already have been two PRs, one even got accepted but was the reverted for a quite lazy reason, see: #71, #78, #82
Related
- https://github.com/source-foundry/Hack/issues/687
Link to font source
https://github.com/source-foundry/Hack
Link to font license
https://github.com/source-foundry/Hack/blob/master/LICENSE.md
Additional context
No response
reverted
Do you have a solution in mind? I don't really see an option if NPM doesn't allow the word Hack in their package names, nor do I wish to take the liberty of renaming a font arbitrarily.
You're right, NPM is quite limited in that regard, one problem is certainly the missing destinction between the name and proper display name, that would certainly be the best solution. I'm not sure if displayName is a proper key in package.json, there are some hints that people are using this, but it doesn't seem to be part of the "specification"...
Otherwise we need to live / work with the inferior infrastructure...
Why not using h4ck or something similar and make sure to use the real name in the description field and hope it's findable using search engines using / indexing this field...
The upstream is certainly not that active any more to obtain approval from it...
Unfortunately, h4ck is also blocked 😆 I don't really have the bandwidth to maintain some custom name mapping of Hack, so I don't think the end result of this will change until NPM updates their filter (which they have admitted is very outdated but this isn't really a priority for them either).
@ayuhito : Is there any open issue for these filters at NPM that could be linked here? "hack" itself should be a valid package indentifier (check https://github.com/npm/validate-npm-package-name for reference). But I understand that it's a problem of the registry itself?
It's an outdated filter system with the registry itself. I've chatted with the NPM support folks about it but it's not on their list of priorities.