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
UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 742): UnableToResolveError: Unable to resolve module prop-types from /home/********/Downloads/react-native-phone-verification-master/example/node_modules/react-native-emoji/index.js: Module does not exist in the module map or in these directories:
/home/**********/Downloads/react-native-phone-verification-master/example/node_modules
Delete the node_modules folder: rm -rf node_modules && npm install.
Reset packager cache: rm -fr $TMPDIR/react-* or npm start -- --reset-cache.
(node:13747) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled willterminate the Node.js process with a non-zero exit code.
I have Follow all these three steps as but still faceing same error .
The text was updated successfully, but these errors were encountered:
UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 742): UnableToResolveError: Unable to resolve module prop-types from /home/********/Downloads/react-native-phone-verification-master/example/node_modules/react-native-emoji/index.js: Module does not exist in the module map or in these directories:
/home/**********/Downloads/react-native-phone-verification-master/example/node_modules
This might be related to facebook/react-native#4968
To resolve try the following:
watchman watch-del-all
.node_modules
folder:rm -rf node_modules && npm install
.rm -fr $TMPDIR/react-*
ornpm start -- --reset-cache
.(node:13747) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled willterminate the Node.js process with a non-zero exit code.
I have Follow all these three steps as but still faceing same error .
The text was updated successfully, but these errors were encountered: