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
I recently upgraded to React Native v0.40 (running on a PC), and am now having issues with Crypto-Js, as explained below. It was working fine before the upgrade, and functionally still seems to be working, but React is throwing errors.
I've tried uninstalling/re-installing the module ("npm uninstall/install crypto-js"), no change.
Based on some google/Stack-Overflowing I also tried "npm install -g crypto-js --save" but that didn't fix anything
I can run Android on my PC in the simulator just fine (and I've verified the Crypto is working), but when I try to package the app I get:
Unable to resolve module crypto-js/md5 from /private/tmp/sandbox/workspace/app/screens/LoginPage.js: Module does not exist in the module map or in these directories:
/private/tmp/sandbox/workspace/node_modules/crypto-js
Thanks for any help people have!
The text was updated successfully, but these errors were encountered:
I recently upgraded to React Native v0.40 (running on a PC), and am now having issues with Crypto-Js, as explained below. It was working fine before the upgrade, and functionally still seems to be working, but React is throwing errors.
I've tried uninstalling/re-installing the module ("npm uninstall/install crypto-js"), no change.
Based on some google/Stack-Overflowing I also tried "npm install -g crypto-js --save" but that didn't fix anything
Running "npm list" gives: npm ERR! extraneous: [email protected]
I can run Android on my PC in the simulator just fine (and I've verified the Crypto is working), but when I try to package the app I get:
Unable to resolve module crypto-js/md5 from /private/tmp/sandbox/workspace/app/screens/LoginPage.js: Module does not exist in the module map or in these directories:
/private/tmp/sandbox/workspace/node_modules/crypto-js
Thanks for any help people have!
The text was updated successfully, but these errors were encountered: