Hacker News new | comments | show | ask | jobs | submit login

Shouldn't the package be called "segment.io"? I'd hate to see every startup with an API trying to grab generic names on package repositories.

That said, it looks like someone else beat you to getting "analytics" for a README.

Perhaps you could make it so segment.io isn't the only option, or merge a pull request that does this, and ask SlexAxton to release the name, as suggested by izs? https://npmjs.org/doc/disputes.html

Edit: also npm is increasingly being used for browser packages. I'm not sure what to do when a browser and server component share the same name.

+1, give up on analytics.js and pick a brand name for the script. It's a good idea, seems well implemented and supported -- we will use it! You're obviously interested in marketing, and using the name analytics.js over segmentio.js seems to serve solely as a thin veil over SEO blog posts. Funny thing is, we like your script and we'll upvote you either way. Change the name!

> npm is increasingly being used for browser packages.

What is a browser package?

If you mean something that's intended to be fed through browserify, it should start with browserify- or end with -browserify

If you mean something like bower or component, which one should be standardized? Hell, both use the same component.json file but they do so in completely different ways

Browserify has a fairly generic format, and some projects are trying to piggyback off of browserify. Also browserify is long and people like to keep package names short. That does simplify things, though...


With upcoming replacement for ga.js (tracker for Google Analytics) is called analytics.js as well, this confusion is about to get messier.

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact