You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd like to spend some time on maintaining Hammer.js and making it a bit better. I'm also interested in react-hammerjs which is maintained in separate repository.
The forked package name is @squadette/hammerjs.
The goals of development are very limited:
fix very well known bugs;
do not break things for people;
improve documentation to help people to better debug their issues;
modernize build system to allow for improved velocity.
The development is based on 2.0.8 (the last released version). Namespaced package name is used (@squadette/hammerjs). The first milestone is going to be 2.1.0, described in a separate tracking issue.
Master branch of original repository contains A LOT of changes that were aimed at HammerJS 3.0. Unfortunately, packaged master breaks for me, so as a first step we'll begin with clean slate of 2.0.8 and then see how it goes.
Hello,
I'd like to spend some time on maintaining Hammer.js and making it a bit better. I'm also interested in react-hammerjs which is maintained in separate repository.
The forked package name is
@squadette/hammerjs
.The goals of development are very limited:
The development is based on 2.0.8 (the last released version). Namespaced package name is used (
@squadette/hammerjs
). The first milestone is going to be 2.1.0, described in a separate tracking issue.Master branch of original repository contains A LOT of changes that were aimed at HammerJS 3.0. Unfortunately, packaged master breaks for me, so as a first step we'll begin with clean slate of 2.0.8 and then see how it goes.
Documentation is also updated as a fork of original website: https://squadette.github.io/hammer.js/.
You can help by testing pre-release version:
Thank you,
The text was updated successfully, but these errors were encountered: