Skip to content

Conversation

@wunderkind2k1
Copy link

Hi.

I noticed that hammer.js has a transitive dependency to jquery 2.2.1 through jquery.hammer.js.
This should fix it. I am not sure how we can check against regressions. Any idea?

It this PR works and jquery.hammer.js is published to npm and hammer.js updates its version of jquery.hammer.js this issue: hammerjs/hammer.js#1138 can be solved I guess.

Hope I am not badly wrong.

@wunderkind2k1
Copy link
Author

@jtangelder are you still working on this? It has been rather quiet around hammer.js and its suprojects lately.

@Ig0r-M-magic42
Copy link

@wunderkind2k1 i see this has not been updated for a long time, do you perhaps have a more up to date forked version ?

@wunderkind2k1
Copy link
Author

@Ig0r-M I am sorry but I ain't have got a forked version. I am not working on that project which uses hammerjs anymore. As far as I remember we only required hammerjs as a transitive dependency during selenium (or puppeteer) tests.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants