-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
HammerJS versioning is confusing #1053
Comments
we'll be rolling out a major update, possibly a v2.1 soon, that should iron out all these inconsistencies. |
@arjunkathuria to be honest I don't really see any activity regarding to the whole project. |
Perhaps not, but certainly coughing up blood from what I've seen. :( |
The most recent version of Hammer is the one available from github source. Please note, The Maintainers of the project are currently under a lot load at their respective work places. If it's something that can be fixed by an individual willing to put in the time, perhaps something small, a PR is the most logical way to help-out until the next development burst. Thank you for your continued patience, everyone. |
@arjunkathuria Any reason they cannot just publish the latest to npm? |
The conservative development fork is at squadette#1 |
There are diffs, because the npm package _version_ is out of sync with the code (only the version number is inconsistent, it appears); this has been reported 3+ years ago in hammerjs/hammer.js#1053, but not progress. Should probably try to find a replacement lib, but this works "enough"…
Hi,
Checking this page:
https://www.npmjs.com/package/hammerjs
It says:
Hammer.js 2.0.6
However:
2.0.8 is the latest of 26 releases
Now:
npm install hammerjs and inside hammer.js:
/*! Hammer.JS - v2.0.7 - 2016-04-22
WTF?
The text was updated successfully, but these errors were encountered: