Unable to resolve module toolbar-android
See original GitHub issueEnvironment
Platform: Android react-native: 0.61.0 react-native-vector-icons: 7.0.0
Description
Error: Unable to resolve module ./toolbar-android
from node_modules/react-native-vector-icons/lib/create-icon-set.js
Issue Analytics
- State:
- Created 3 years ago
- Reactions:3
- Comments:9
Top Results From Across the Web
Unable to resolve module `@react-native-community/toolbar ...
this issue is fixed on version "^7.1.0" and there is no need to install the @react-native-community/toolbar-android .
Read more >Unable to resolve module `@react-native-community/toolbar ...
After upgrading to the new version 6.7.0 , bundling fails at: error: Error: Unable to resolve module `@react-native-community/toolbar-android` ...
Read more >Unable to resolve module `@react-native-community/toolbar ...
Coding example for the question Error: Unable to resolve module ... You can install the @react-native-community/toolbar-android by using the below command:
Read more >react-native-community/toolbar-android - npm
A React Native Component for Android Toolbar. Latest version: 0.2.1, last published: a year ago.
Read more >unable to resolve module react native - You.com | The search ...
Note: Both of these solutions are temporary and soonly this bug will be fixed and there is no need to install the toolbar-android...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
For me the problem appeared when going from 6.6.0 -> 7.0.0.
Still trying to resolve it.
RN: 0.62.2 Node: 12.16.3 OS: Windows 10 64 bit Pro
Also tested it on Mac and it worked fine there.
Edit: Running
react-native start --reset-cache
first, seems to have done the trick.Same issue with 7.0.0 RN 0.63.2