RealOrangeOne/react-native-mock

Cannot find module 'react/lib/ReactComponentTreeHook' from 'ReactDebugTool.js'

Open

#141 opened on Jul 19, 2017

View on GitHub
 (35 comments) (43 reactions) (0 assignees)JavaScript (151 forks)github user discovery
Bughelp wanted

Repository metrics

Stars
 (567 stars)
PR merge metrics
 (PR metrics pending)

Description

After adding and importing this lib, testing with jest shows errors for all test suites:

  ● Test suite failed to run

    Cannot find module 'react/lib/ReactComponentTreeHook' from 'ReactDebugTool.js'
      
      at Resolver.resolveModule (node_modules/jest-resolve/build/index.js:179:17)
      at Object.<anonymous> (node_modules/react-addons-perf/node_modules/react-dom/lib/ReactDebugTool.js:16:30)

Part of package.json:

{
  "dependencies": {
    "react": "16.0.0-alpha.12", 
    "react-native": "0.46.3",
    ...
  }
  "devDependencies": {
    "jest": "^20.0.4",                               // 20.0.4
    "react-dom": "16.0.0-alpha.12",
    "react-native-mock": "^0.3.1",                   // 0.3.1
    "react-test-renderer": "16.0.0-alpha.12",
    ...
  }
}

Those errors are raised from react-addons-perf which is depended by react-native-mock. The version of react-addons-perf is 15.4.2. I'm not sure whether it is related to the version of react (16.0.0-alpha.12).

Contributor guide

Research direction
Check version compatibility between react addons perf (15.4.2) and React 16.0.0 alpha.12. The missing module 'react/lib/ReactComponentTreeHook' was removed in React 16. Consider updating react addons perf to a version compatible with React 16 or mock the missing module in jest configuration.
Tech stack
javascriptreactjest
Domain
testingmobile
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
JavaScriptReactJest
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60