-
Notifications
You must be signed in to change notification settings - Fork 255
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add to npm #40
Comments
+1 |
4 similar comments
+1 |
+1 |
+1 |
+1 |
+1 |
Until github creates a "like" style button or something like stackoverflow, that's the best there is. I have nothing better to contribute except to express that the original poster was not alone in their request. Seems weird that feature doesn't exist. |
On Bugzilla and JIRA you have votes, and even on Google Code you could star issues. The closest equivalent on Github is subscribing to an issue, though it's kind of passive compared to the +1. In any case, after so much feedback, this will be added to NPM in the next release. :) |
+1 :) |
Hey, folks! After an unreasonable amount of time, this issue is finally (mostly) addressed in the open PR #64. To any interested person: please feel free to review the PR and leave comments (there are already some open questions there), or it will be merged mostly as-is within the next two weeks. Thanks, and sorry for the delay! |
I guess this should be officially added to npm? There are a couple folks who registered unofficial clones, but it might be best to have the official one in the registry, yes?
+1 (or make a pull request!) if you want this to happen. (Maybe pair this with #32?)
The text was updated successfully, but these errors were encountered: