Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Npm link cause "Unable to resolve module `AccessibilityInfo` "
See original GitHub issueIs this a bug report?
Feels like it is a bug.
Environment
react-native -v:react-native-cli: 2.0.1 react-native: 0.46.4node -v:v8.1.3npm -v:5.3.0
-
Target Platform: *
-
Development Operating System: macOS 10.12.5 & Windows 10 64bit
Steps to Reproduce
There is a RN Project A and Denpendency B.
B is abstracted from A, it works properly before.
Now B has a dependency on RN.
Project A install Dependency B using npm link ../B && npm install ../B --save.
Structure as below:
|–A
|–|–node_modules
|-------|–RN
|-------|–B
|----------|–node_modules
|---------------|–RN
Run with react-native start
Expected Behavior
Everything goes fine.
Actual Behavior
Error pops up as error: bundling failed: "Unable to resolve module "AccessibilityInfo" from "/path/to/A/node_modules/react-native/Libraries/react-native/react-native-implementation.js": Module does not exist in the module map.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:4
- Comments:7 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I don’t know if someone told that before me but downgrading from
0.56.0to0.55.4solved this issue for me. 😃I don’t think that it is a dublicate of an multiple years old issue. Because the only solution of the old issue was to downgrade version. Downgrading is only a temporary fix, but no permanent solution. The problem seems to be the same, it doesn’t mean that reason is identacally, too.