You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Microsoft Edge Version 95.0.1020.53 (Official build) (arm64)
Steps to reproduce
To reproduce:
Download now-ui-pro-react-native-v1.4.0.zip and extract to now-ui-pro-react-native folder
Change directory to newly extracted now-ui-pro-react-native folder
Run npm install
Once npm completes installation, then run expo start
Browser opens as expected with no errors
Opening app on Android device through Expo Go or on ios simulator yields the same error:
Android Bundling failed 20668ms
Unable to resolve module @unimodules/react-native-adapter from /Users/mlfowler/Documents/workspaces/now-ui-pro-react-native/node_modules/@unimodules/core/build/AdapterProxy.js: @unimodules/react-native-adapter could not be found within the project.
If you are sure the module exists, try these steps:
Clear watchman watches: watchman watch-del-all
Delete node_modules and run yarn install
Reset Metro's cache: yarn start --reset-cache
Remove the cache: rm -rf /tmp/metro-*
1 | export * from '@unimodules/react-native-adapter';
What is expected?
Expectation is that mobile app will run and display properly once npm install has been run using included package.json file.
Expectation is that clean project should work properly out-of-the-box without having to install any new dependencies.
What is actually happening?
Mobile app is not running properly when viewing on Expo Go or ios simulator. Is erroring out with the following:
Android Bundling failed 20668ms
Unable to resolve module @unimodules/react-native-adapter from /Users/mlfowler/Documents/workspaces/now-ui-pro-react-native/node_modules/@unimodules/core/build/AdapterProxy.js: @unimodules/react-native-adapter could not be found within the project.
Solution
Manually working through all the dependencies the project is missing.
Additional comments
The theme looks great, and I want to use it. I just can't seem to get it to load and run properly due to missing dependencies.
The text was updated successfully, but these errors were encountered:
Version
1.4.0
Reproduction link
https://jsfiddle.net/pfq9za34/
Operating System
macOS Big Sur 11.6
Device
Samsung Galaxy S20+
Browser & Version
Microsoft Edge Version 95.0.1020.53 (Official build) (arm64)
Steps to reproduce
To reproduce:
Download now-ui-pro-react-native-v1.4.0.zip and extract to now-ui-pro-react-native folder
Change directory to newly extracted now-ui-pro-react-native folder
Run
npm install
Once npm completes installation, then run
expo start
Browser opens as expected with no errors
Opening app on Android device through Expo Go or on ios simulator yields the same error:
Android Bundling failed 20668ms
Unable to resolve module @unimodules/react-native-adapter from /Users/mlfowler/Documents/workspaces/now-ui-pro-react-native/node_modules/@unimodules/core/build/AdapterProxy.js: @unimodules/react-native-adapter could not be found within the project.
If you are sure the module exists, try these steps:
What is expected?
Expectation is that mobile app will run and display properly once npm install has been run using included package.json file.
Expectation is that clean project should work properly out-of-the-box without having to install any new dependencies.
What is actually happening?
Mobile app is not running properly when viewing on Expo Go or ios simulator. Is erroring out with the following:
Android Bundling failed 20668ms
Unable to resolve module @unimodules/react-native-adapter from /Users/mlfowler/Documents/workspaces/now-ui-pro-react-native/node_modules/@unimodules/core/build/AdapterProxy.js: @unimodules/react-native-adapter could not be found within the project.
Solution
Manually working through all the dependencies the project is missing.
Additional comments
The theme looks great, and I want to use it. I just can't seem to get it to load and run properly due to missing dependencies.
The text was updated successfully, but these errors were encountered: