Usage of react-panresponder-web, which is incompatible with React newer than 16

Open
#9 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
32/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript, react
Domain
frontend

Research direction

Start by inspecting the react-panresponder-web dependency and its use of react-dom/unstable-native-dependencies and injectEventPluginsByName. Compare the current react-native-web responder event implementation and useResponderEvents hook; done means the library works with React versions newer than 16.

Written by the indexing model from the issue text.

Description

I see this library no longer works with a newer version of React than 16. I tried to debug this issue, and found the following:

This is because it uses react-panresponder-web, which in turn depends on react-dom/unstable-native-dependencies (that no longer exists). It seems to use injectEventPluginsByName and a forked version of the react-native-web ResponderEventPlugin.
injectEventPluginsByName was removed in some newer version of React, and ResponderEventPlugin was removed in this commit and replaced with a useResponderEvents hook.

I attempted to fix this but i am not quite sure how to proceed. I see that react-native-web now has a new Responder Event System implementation: https://github.com/necolas/react-native-web/issues/1568. This uses hooks, but it should be possible to wrap this around a class component as well.

I would be very grateful if you could fix this issue, or atleast give me a few pointers on how to proceed with fixing this.

Dominant language
JavaScript
Stars
58
Forks
6
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from arqex/react-interactable

All issues in arqex/react-interactable

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.