Add bower and npm package info

[cassidyjames]

I published this to npm and bower because I needed it in a project and noticed nothing lived at font-linux on either. Here are the config files, and I'm happy to keep them as up to date as possible. 😄

[lukas-w]

Is there a way to have the packages point to github.com/Lukas-W/font-linux instead of github.com/cassidyjames/font-linux? Or do I have to be the package's owner for that? In that case, can we unpublish yours, publish it with me as the owner instead, and grant write access to you? Sorry, I've never worked with bower or npm before. Opinions or explanations/instructions welcome. 👍

Also, I'd be interested in setting up a mechanism for automatically publishing new versions to both bower and npm (with Travis?) when I push a new tag to GitHub.

[tresf]

Also, I'd be interested in setting up a mechanism for automatically publishing new versions to both bower and npm (with Travis?) as when I push a new tag to GitHub.

I'd like to know how to do this as well. 👍

[jgillich]

ping @cassidyjames

[jgillich]

Automatically publishing tags could be done with Travis: https://docs.travis-ci.com/user/deployment/npm/

[jgillich]

@lukas-w Do you have an npm account that he could transfer to?

[lukas-w]

@jgillich Yes, my npm username is lukas-w. @cassidyjames Any chance you could transfer the packages?

[lukas-w]

Closing in favor of #28.

[tresf]

Closing in favor of #28.

Automatically publishing tags could be done with Travis: https://docs.travis-ci.com/user/deployment/npm/

You may want to open a separate issue for auto-publishing.

[cassidyjames]

@lukas-w sorry for the delayed response, apparently my GitHub notifications were going to my work email and being filtered out. 😛

Is there anything for me to do here, like unpublishing or transferring ownership?

[lukas-w]

Is there anything for me to do here, like unpublishing or transferring ownership?

Yes, please transfer ownership of the npm package to lukas-w, or just "add" me if that's the same thing – probably a good idea to keep a second owner.

Not sure about bower, @jgillich says bower is dead. However, https://bower.io/stats/ suggests otherwise:

[jgillich]

I remember the bower maintainer saying that development had stopped and that npm should be used instead, seems like some people still have reasons to go on with it (bower/bower#2298).

[tresf]

I remember the bower maintainer saying that development had stopped and that npm should be used instead, seems like some people still have reasons to go on with it (bower/bower#2298).

From my little corner of the world... I've personally never heard bower used in conversations with other developers although I do hear "browserify" on occasion.

I author a JS API myself and I've never been asked to provide it for bower other than in a generic npm request similar to this one.

Bower's main claim is the flat-dependency structure can help alleviate the burden on the browser, so there's good argument for it, I just don't hear about it all that much.

Then again, 80,000 installs per day on average is quite impressive. NPM is arguably higher by a factor of 5 or 10.

[jgillich]

Since version 3, npm also flattens the dependency tree, so that argument does not hold up anymore. The stats are also highly skewed in favour of bower since npm is usually installed from distribution repositories (and most of these are installs by CI, not actual users).

I'm not saying we should not support bower, I just didn't do it because I think most people have moved on by now. It certainly doesn't hurt to also publish to bower if there are people using it.

[lukas-w]

@cassidyjames Can you please transfer ownership of the npm package?

[Finii]

Can you please transfer ownership of the npm package?

Obviously that has been done:

$ npm owner ls font-logos
lukas-w <lukaswhl@gmail.com>

(Just mentioning for people like me who wonder....)

[lukas-w]

Actually it hasn't, this was before the rename from font-linux which five years later is still owned by @cassidyjames 😅

[Finii]

🤦‍♀️ I need to read ;-)

[cassidyjames]

I regained access to my npm account (it was unused for about 7 years...) and marked the package as deprecated, and invited @lukas-w as a maintainer. I don't see a way to transfer it, and GitHub won't let me transfer the repo itself to @lukas-w since it's a fork for @lukas-w's original repo anyway.

Hopefully that gets you where you need to be, but if not, I'm willing to do whatever is needed. :)

[tresf]

GitHub won't let me transfer the repo itself to @lukas-w since it's a fork

FYI, GitHub does allow this but only with manual support intervention using the Contact GitHub option.

[tresf]

GitHub won't let me transfer the repo itself to @lukas-w since it's a fork

FYI, GitHub does allow this but only with manual support intervention using the Contact GitHub option.

Actually, nevermind, I'm thinking of repointing the upstream, which isn't what you're talking about, please disregard.

[lukas-w]

@cassidyjames thank you! I've changed the deprecation message to point to the new project name. 🍻

[cassidyjames]

@lukas-w great! I've actually removed myself as a maintainer as well since I've obviously not been maintaining the npm package. :)