Is this library still actively maintained?

[e-e-e]

There has not been much activity in this repo for the last few months and there are many open issues. Is it still actively maintained?

[runspired]

@e-e-e unfortunately all the maintainers have been quite busy. I had hopes of releasing a new version a few years ago but work took me away from a focus on mobile. I'm happy to help someone new pick up the banner though!

[runspired]

cc @arjunkathuria @arschmitz @jtangelder for visibility.

[jongmoon]

@runspired I'm very happy to see contributor's comment here. I thought it is not active any more.

I sent email or twitter message to @arjunkathuria @arschmitz @jtangelder for asking library's plan
6months ago. but I could not receive any response because we want to contribute and solve issues unresolved.

As if our team had done the following before

• fix : #768 issue
• Suggest change event flow
• fix #768 issue (Manager.off method)
• test: fix wrong test filepath
• add feature that touch-action style is restored in Hammer.destroy
• fix(Manager): Hammer.defaults.cssProps are restored on destory
• feat(TouchAction) touch-action style is restored in Hammer.destroy
• fix(input): fix pointerEvent bug

We are using hammer.js very tightly in our component (egjs-axes, egjs-flicking and egjs-view360,...). So we've had plan to manage new hammer.js as fork project(https://github.com/naver/hammer.js).

But if this project has plan to activate again. We want to contribute here.

[DavidPeicho]

It would be a wonderful idea if we could continue to contribute here. There are more than 2K forks, and I am sure a lot of them, like yours @jongmoon, bring a lot. We would need some maintainers for reviewing the PR, and for merging them.

[runspired]

I would be happy to review things, I would also be happy to discuss the plans I had for Hammer 3.x that I never got a chance to pursue. We spiked them but no one had time to drive it at the time.

[ArtemBernatskyy]

cc @arjunkathuria @arschmitz @jtangelder

[SampsonCrowley]

At the very least, we need to add an ES Module build

[squadette]

I'm going to spend some time on maintaining Hammer.js. Here is the tracking issue that describes my plan of action: squadette#1

Thank you,

[runspired]

@squadette happy to help bring someone in