# \[Archive\] Unable to resolve module crypto

**URL:** <https://builder.metamask.io/t/archive-unable-to-resolve-module-crypto/1895>\
**Category:** Embedded Wallets (Web3Auth)\
**Created:** [July 11, 2023, 1:29pm UTC](https://builder.metamask.io/t/archive-unable-to-resolve-module-crypto/1895 "2023-07-11T13:29:11Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![yammonabd](https://avatars.discourse-cdn.com/v4/letter/y/e9a140/32.png) [@yammonabd](https://builder.metamask.io/u/yammonabd)\
**Post date:** [July 11, 2023, 1:29pm UTC](https://builder.metamask.io/t/archive-unable-to-resolve-module-crypto/1895/1 "2023-07-11T13:29:11Z")

</div>

> **🏛 Archived Content from Web3Auth Community**
> 
> This topic was originally posted by **yammonabd** on 7/11/2023.  
> This content has been migrated from our previous community forum to preserve valuable discussions.

* * *

**Full Error:**  
Error: undefined Unable to resolve module crypto from /node\_modules/@toruslabs/eccrypto/dist/eccrypto.cjs.js: crypto could not be found within the project or in these directories:  
node\_modules  
76 | });  
77 |

> 78 | ;// CONCATENATED MODULE: external “crypto”  
> | ^  
> 79 | const external\_crypto\_namespaceObject = require(“crypto”);  
> 80 | var external\_crypto\_default = /_# **PURE** _/ **webpack\_require**.n(external\_crypto\_namespaceObject);  
> 81 | ;// CONCATENATED MODULE: external “elliptic”]

* * *

**Info**

- SDK Version: 4.0.0
- Bare Version: 0.70.0
- Screenshots of error:  

[![Simulator Screenshot - iphone x - 2023-07-11 at 17.27.46](https://canada1.discourse-cdn.com/flex011/uploads/metamaskbuilderhub/original/2X/8/80d635bb6f5cf614b2b96396574683963fccd808.png)
Simulator Screenshot - iphone x - 2023-07-11 at 17.27.461125×2436 159 KB
](https://community.web3auth.io/community/community/uploads/default/original/2X/b/b61465c948ba7bb599da7b9c766f8061619f215b.png "Simulator Screenshot - iphone x - 2023-07-11 at 17.27.46")

**Please provide the Web3Auth initialization and login code snippet below:**  
const web3auth = new Web3Auth(WebBrowser, {  
clientId,  
network: OPENLOGIN\_NETWORK.TESTNET, // or other networks  
});

---

<div class="post-metadata">

**Author:** ![vjgee](https://avatars.discourse-cdn.com/v4/letter/v/b5e925/32.png) [@vjgee](https://builder.metamask.io/u/vjgee)\
**Post date:** [July 11, 2023, 3:18pm UTC](https://builder.metamask.io/t/archive-unable-to-resolve-module-crypto/1895/2 "2023-07-11T15:18:22Z")

</div>

@yammonabd Thanks for your post.

Your issue has been forwarded to our team and we will get back with further updates once more information becomes available.

---

<div class="post-metadata">

**Author:** ![b5g](https://avatars.discourse-cdn.com/v4/letter/b/41988e/32.png) [@b5g](https://builder.metamask.io/u/b5g)\
**Post date:** [July 12, 2023, 7:12am UTC](https://builder.metamask.io/t/archive-unable-to-resolve-module-crypto/1895/3 "2023-07-12T07:12:00Z")

</div>

Facing same issue with using expo and `@web3auth/react-native-sdk` 4.0.0.  
Is there any quick workaround so I wouldn’t be stuck at this point?

---

<div class="post-metadata">

**Author:** ![chai](https://avatars.discourse-cdn.com/v4/letter/c/919ad9/32.png) [@chai](https://builder.metamask.io/u/chai)\
**Post date:** [July 13, 2023, 10:06am UTC](https://builder.metamask.io/t/archive-unable-to-resolve-module-crypto/1895/4 "2023-07-13T10:06:04Z")

</div>

Please use the following config as present in our demo:  
Metro: [https://github.com/Web3Auth/web3auth-react-native-sdk/blob/master/demo/rn-expo-example/metro.config.js](https://github.com/Web3Auth/web3auth-react-native-sdk/blob/master/demo/rn-expo-example/metro.config.js)  
Bare: [https://github.com/Web3Auth/web3auth-react-native-sdk/blob/master/demo/rn-bare-example/metro.config.js](https://github.com/Web3Auth/web3auth-react-native-sdk/blob/master/demo/rn-bare-example/metro.config.js)